From: Avi Kivity <avi@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: virtualization@lists.linux-foundation.org,
Anthony Liguori <aliguori@us.ibm.com>,
linux-pci@vger.kernel.org, Matt Carlson <mcarlson@broadcom.com>,
linux-kernel@vger.kernel.org,
Jesse Barnes <jbarnes@virtuousgeek.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>,
Tejun Heo <tj@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Bjorn Helgaas <bjorn.helgaas@hp.com>
Subject: Re: [PATCH for-2.6.35] virtio-pci: disable msi at startup
Date: Wed, 23 Jun 2010 18:53:46 +0300 [thread overview]
Message-ID: <4C222E0A.8060803@redhat.com> (raw)
In-Reply-To: <20100623154311.GD30526@redhat.com>
On 06/23/2010 06:43 PM, Michael S. Tsirkin wrote:
>
>
>>> If/when we use more registers, we can update driver to clear them on start.
>>>
>>>
>> The kdump kernel may not load drivers for those extra devices.
>>
> Then we don't care about clearing them?
>
We do, if the device has a side effect (like blasting out noise through
loudspeakers).
Anyway, just a suggestion.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-06-23 15:54 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-10 15:22 [PATCH for-2.6.35] virtio-pci: disable msi at startup Michael S. Tsirkin
2010-06-10 15:34 ` Jesse Barnes
2010-06-10 15:34 ` Jesse Barnes
2010-06-23 13:59 ` Avi Kivity
2010-06-23 13:59 ` Avi Kivity
2010-06-23 13:59 ` Michael S. Tsirkin
2010-06-23 14:21 ` Avi Kivity
2010-06-23 14:21 ` Avi Kivity
2010-06-23 14:43 ` Michael S. Tsirkin
2010-06-23 14:43 ` Michael S. Tsirkin
2010-06-23 15:15 ` Avi Kivity
2010-06-23 15:26 ` Michael S. Tsirkin
2010-06-23 15:35 ` Avi Kivity
2010-06-23 15:43 ` Michael S. Tsirkin
2010-06-23 15:53 ` Avi Kivity
2010-06-23 15:53 ` Avi Kivity [this message]
2010-06-23 15:43 ` Michael S. Tsirkin
2010-06-23 15:51 ` Jesse Barnes
2010-06-23 15:51 ` Jesse Barnes
2010-06-23 15:35 ` Avi Kivity
2010-06-23 15:26 ` Michael S. Tsirkin
2010-06-23 15:15 ` Avi Kivity
2010-06-23 13:59 ` Michael S. Tsirkin
-- strict thread matches above, loose matches on Subject: below --
2010-06-10 15:22 Michael S. Tsirkin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C222E0A.8060803@redhat.com \
--to=avi@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=bjorn.helgaas@hp.com \
--cc=davem@davemloft.net \
--cc=jbarnes@virtuousgeek.org \
--cc=kaneshige.kenji@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mcarlson@broadcom.com \
--cc=mst@redhat.com \
--cc=rjw@sisk.pl \
--cc=tj@kernel.org \
--cc=virtualization@lists.linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.