xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: Paul Durrant <Paul.Durrant@citrix.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
	Wei Liu <wei.liu2@citrix.com>, Jan Beulich <JBeulich@suse.com>,
	Andrew Cooper <Andrew.Cooper3@citrix.com>
Subject: Re: [PATCH] x86/vMSI-X: write snoops should ignore hvm_mmio_internal() requests
Date: Tue, 26 Apr 2016 15:43:40 +0100	[thread overview]
Message-ID: <20160426144340.GM20763@citrix.com> (raw)
In-Reply-To: <ac22c39e0c1d4e78a4b4ce7988b9185b@AMSPEX02CL03.citrite.net>

On Tue, Apr 26, 2016 at 03:40:29PM +0100, Paul Durrant wrote:
> > -----Original Message-----
> > From: Jan Beulich [mailto:JBeulich@suse.com]
> > Sent: 26 April 2016 15:39
> > To: xen-devel
> > Cc: Andrew Cooper; Paul Durrant; Wei Liu
> > Subject: [PATCH] x86/vMSI-X: write snoops should ignore
> > hvm_mmio_internal() requests
> > 
> > Those aren't actual I/O requests (and hence are of no interest here
> > anyway). Since they don't get copied into struct vcpu, looking at that
> > copy reads whatever was left there. Use the state of the request to
> > determine its validity.
> > 
> > Signed-off-by: Jan Beulich <jbeulich@suse.com>
> 
> Reviewed-by: Paul Durrant <paul.durrant@citrix.com>
> 

Release-acked-by: Wei Liu <wei.liu2@citrix.com>

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

      reply	other threads:[~2016-04-26 14:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-26 14:39 [PATCH] x86/vMSI-X: write snoops should ignore hvm_mmio_internal() requests Jan Beulich
2016-04-26 14:40 ` Paul Durrant
2016-04-26 14:43   ` Wei Liu [this message]

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=20160426144340.GM20763@citrix.com \
    --to=wei.liu2@citrix.com \
    --cc=Andrew.Cooper3@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=Paul.Durrant@citrix.com \
    --cc=xen-devel@lists.xenproject.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).