qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Graf <agraf@suse.de>
To: Gavin Shan <gwshan@linux.vnet.ibm.com>, qemu-devel@nongnu.org
Cc: aik@ozlabs.ru, alex.williamson@redhat.com
Subject: Re: [Qemu-devel] [PATCH] sPAPR/IOMMU: Fix TCE entry permission
Date: Mon, 14 Jul 2014 19:19:45 +0200	[thread overview]
Message-ID: <53C41131.8090102@suse.de> (raw)
In-Reply-To: <1405339783-4501-1-git-send-email-gwshan@linux.vnet.ibm.com>


On 14.07.14 14:09, Gavin Shan wrote:
> The permission of TCE entry should exclude physical base address.
> Otherwise, unmapping TCE entry can be interpreted to mapping TCE
> entry wrongly for VFIO devices.
>
> Signed-off-by: Gavin Shan <gwshan@linux.vnet.ibm.com>

Thanks, applied to ppc-next-2.1.


Alex

      parent reply	other threads:[~2014-07-14 17:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-14 12:09 [Qemu-devel] [PATCH] sPAPR/IOMMU: Fix TCE entry permission Gavin Shan
2014-07-14 15:35 ` Alex Williamson
2014-07-14 17:19 ` Alexander Graf [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=53C41131.8090102@suse.de \
    --to=agraf@suse.de \
    --cc=aik@ozlabs.ru \
    --cc=alex.williamson@redhat.com \
    --cc=gwshan@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.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).