From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Andrew Sorensen <andrewx192@gmail.com>
Cc: xen-devel@lists.xen.org
Subject: Re: msitranslate: question about qemu-upstream and pv support
Date: Mon, 4 Aug 2014 10:26:05 -0400 [thread overview]
Message-ID: <20140804142605.GG18425@laptop.dumpdata.com> (raw)
In-Reply-To: <53D185B8.3000505@gmail.com>
On Thu, Jul 24, 2014 at 03:16:24PM -0700, Andrew Sorensen wrote:
> I noticed that the patches for msitranslate do not seem to have made it
> into qemu-upstream. The logic still exists in
> xen/drivers/passthrough/io.c, though documentation suggests MSI-INTx
> translation is only implemented for HVM guests.
>
> Based on the disabling of MSI-INTx by default, it seems safe to assume
> that MSI translation is only supported under qemu-xen-traditional, and
> only for HVM guests. Is this correct?
My recollection is that it is an optimization. That is - if we do PCI
passthrough - and the device is doing legacy interrpupts - we want
to pass that (as it means updating QEMU) and instead doing an MSI - so
that QEMU is not scheduled in.
But most network cards don't use legacy interrupts. Perhaps the
video cards use it - but for example the i915 is doing MSI and
I would think that radeon and nouvau are moving that way too?
>
> I don't see any mention of this on this wiki page:
> http://wiki.xen.org/wiki/QEMU_Upstream
> #Missing_feature_from_the_good_old_qemu-dm
That looks to be an omission. Do you have an account on the
Wiki to update it? Are you Ok updating it? Thank you!
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
prev parent reply other threads:[~2014-08-04 14:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-24 22:16 msitranslate: question about qemu-upstream and pv support Andrew Sorensen
2014-08-04 14:26 ` Konrad Rzeszutek Wilk [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=20140804142605.GG18425@laptop.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=andrewx192@gmail.com \
--cc=xen-devel@lists.xen.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.