public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Alex Williamson <alex.williamson@redhat.com>,
	kvm@vger.kernel.org, jan.kiszka@siemens.com, jbaron@redhat.com
Subject: Re: [PATCH v2] kvm: Disable MSI/MSI-X in assigned device reset path
Date: Sun, 08 Apr 2012 17:01:36 +0300	[thread overview]
Message-ID: <4F819A40.1010806@redhat.com> (raw)
In-Reply-To: <20120408135324.GA14166@redhat.com>

On 04/08/2012 04:53 PM, Michael S. Tsirkin wrote:
> On Sun, Apr 08, 2012 at 04:41:27PM +0300, Avi Kivity wrote:
> > On 04/08/2012 04:30 PM, Michael S. Tsirkin wrote:
> > > On Sun, Apr 08, 2012 at 04:24:11PM +0300, Avi Kivity wrote:
> > > > On 04/08/2012 04:21 PM, Michael S. Tsirkin wrote:
> > > > > On Sun, Apr 08, 2012 at 04:18:29PM +0300, Avi Kivity wrote:
> > > > > > On 04/08/2012 04:17 PM, Michael S. Tsirkin wrote:
> > > > > > > > 
> > > > > > > > Don't we FLR the device, which ought to disable MSI on the real device?
> > > > > > >
> > > > > > > AFAIK we call pci_reset, which saves device state, does an FLR
> > > > > > > and then restores the state. I think this might include msi as well.
> > > > > > >
> > > > > > >
> > > > > > 
> > > > > > Then that is wrong as well, no?
> > > > >
> > > > > Not as such assuming we disable msi/msix first :)
> > > > 
> > > > I think we need to fix both, no?
> > >
> > > Isn't this what this patch does?
> > 
> > If we change pci_reset() (or a variant that we call) to reset MSI, and
> > update qemu to synchronize from the device after pci_reset(), then we
> > achieve the same result, in a different way.
>
> MSI vectors are set up by kvm in the host. So we should not
> abruptly drop that by a sysfs write: would need to
> synchronise with kvm. Once we do, there's nothing left
> for pci_reset to do.

I'm thinking about this flow:

  FLR the device
  for each emulated register
     read it from the hardware
     if different from emulated register:
        update the internal model (for example, disabling MSI in kvm if
needed)
        set emulated register to hardware value

> > Since reset can change other config space registers, we achieve
> > correctness for more of them.
>
> Which other registers do you have in mind?

BARs for example.  We may have our own reset for this, but isn't copying
the hardware values more trustworthy?

-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2012-04-08 14:01 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-05  3:42 [PATCH v2] kvm: Disable MSI/MSI-X in assigned device reset path Alex Williamson
2012-04-05  7:28 ` Jan Kiszka
2012-04-05  9:34 ` Michael S. Tsirkin
2012-04-05 14:42   ` Alex Williamson
2012-04-05 15:04     ` Michael S. Tsirkin
2012-04-08 13:14 ` Avi Kivity
2012-04-08 13:17   ` Michael S. Tsirkin
2012-04-08 13:18     ` Avi Kivity
2012-04-08 13:21       ` Michael S. Tsirkin
2012-04-08 13:24         ` Avi Kivity
2012-04-08 13:30           ` Michael S. Tsirkin
2012-04-08 13:41             ` Avi Kivity
2012-04-08 13:53               ` Michael S. Tsirkin
2012-04-08 14:01                 ` Avi Kivity [this message]
2012-04-08 14:42                   ` Michael S. Tsirkin
2012-04-08 15:26                     ` Avi Kivity
2012-04-08 15:46                       ` Michael S. Tsirkin
2012-04-08 15:50                         ` Avi Kivity
2012-04-08 16:04                           ` Michael S. Tsirkin
2012-04-08 16:08                             ` Avi Kivity
2012-04-08 17:37                               ` Jan Kiszka
2012-04-08 18:18                                 ` Michael S. Tsirkin
2012-04-08 18:39                                   ` Jan Kiszka
2012-04-08 20:35                                     ` Michael S. Tsirkin
2012-04-09  8:35                                 ` Avi Kivity
2012-04-10 16:55                                   ` Alex Williamson
2012-04-16 14:03 ` Alex Williamson
2012-04-16 14:31   ` Avi Kivity
2012-04-16 15:06   ` Michael S. Tsirkin
2012-04-16 15:10     ` Jan Kiszka
2012-04-16 16:08       ` Michael S. Tsirkin
2012-04-16 16:13         ` Jan Kiszka
2012-04-16 16:36           ` Michael S. Tsirkin
2012-04-16 16:38             ` Jan Kiszka
2012-04-16 17:12               ` Michael S. Tsirkin
2012-04-16 18:47                 ` Jan Kiszka
2012-04-16 16:12     ` Jason Baron
2012-04-16 16:34       ` Michael S. Tsirkin
2012-04-16 19:07     ` Alex Williamson
2012-04-16 19:47       ` Michael S. Tsirkin
2012-04-17  0:55 ` Marcelo Tosatti

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=4F819A40.1010806@redhat.com \
    --to=avi@redhat.com \
    --cc=alex.williamson@redhat.com \
    --cc=jan.kiszka@siemens.com \
    --cc=jbaron@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mst@redhat.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox