Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757173Ab2ECLAK (ORCPT ); Thu, 3 May 2012 07:00:10 -0400 Received: from mx1.redhat.com ([209.132.183.28]:5528 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755404Ab2ECLAI (ORCPT ); Thu, 3 May 2012 07:00:08 -0400 Date: Thu, 3 May 2012 16:29:59 +0530 From: Amit Shah To: "Michael S. Tsirkin" Cc: netdev@vger.kernel.org, Rusty Russell , virtualization@lists.linux-foundation.org, linux-kernel@vger.kernel.org, kvm@vger.kernel.org Subject: Re: [PATCH RFC] virtio-net: remove useless disable on freeze Message-ID: <20120503105959.GM13421@amit.redhat.com> References: <20120404091954.GA3776@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120404091954.GA3776@redhat.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 651 Lines: 17 On (Wed) 04 Apr 2012 [12:19:55], Michael S. Tsirkin wrote: > disable_cb is just an optimization: it > can not guarantee that there are no callbacks. Even then, what's the harm in keeping it? If indeed there's an attempt to raise an interrupt after the host has been notified, it will be suppressed. Also, disable_cb seems to be used elsewhere in the virtio_net.c file, to suit similar purposes. Amit -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/