From: Thomas Huth <thuth@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>,
peter.maydell@linaro.org, agraf@suse.de, aik@ozlabs.ru
Cc: qemu-devel@nongnu.org, qemu-ppc@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] spapr: Only report host/guest IOMMU page size mismatches on KVM
Date: Tue, 4 Jul 2017 16:04:13 +0200 [thread overview]
Message-ID: <417cce4a-de1e-e8f5-96a9-a73d0fbe3446@redhat.com> (raw)
In-Reply-To: <20170704135454.13467-1-david@gibson.dropbear.id.au>
On 04.07.2017 15:54, David Gibson wrote:
> We print a warning if the spapr IOMMU isn't configured to support a page
> size matching the host page size backing RAM. When that's the case we need
> more complex logic to translate VFIO mappings, which is slower.
>
> But, it's not so slow that it would be at all noticeable against the
> general slowness of TCG. So, only warn when using KVM. This removes some
> noisy and unhelpful warnings from make check on hosts with page sizes
> which typically differ from those on POWER (e.g. Sparc).
>
> Reported-by: Peter Maydell <peter.maydell@linaro.org>
> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
> ---
> hw/ppc/spapr_pci.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/hw/ppc/spapr_pci.c b/hw/ppc/spapr_pci.c
> index cc1588d..a52dcf8 100644
> --- a/hw/ppc/spapr_pci.c
> +++ b/hw/ppc/spapr_pci.c
> @@ -1745,7 +1745,8 @@ static void spapr_phb_realize(DeviceState *dev, Error **errp)
> }
>
> /* DMA setup */
> - if ((sphb->page_size_mask & qemu_getrampagesize()) == 0) {
> + if (((sphb->page_size_mask & qemu_getrampagesize()) == 0)
> + && kvm_enabled()) {
Since you've put me on CC: ... too much parenthesis for my taste ;-)
Apart from that,
Reviewed-by: Thomas Huth <thuth@redhat.com>
prev parent reply other threads:[~2017-07-04 14:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-04 13:54 [Qemu-devel] [PATCH] spapr: Only report host/guest IOMMU page size mismatches on KVM David Gibson
2017-07-04 14:04 ` Thomas Huth [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=417cce4a-de1e-e8f5-96a9-a73d0fbe3446@redhat.com \
--to=thuth@redhat.com \
--cc=agraf@suse.de \
--cc=aik@ozlabs.ru \
--cc=david@gibson.dropbear.id.au \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).