From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
Nikunj A Dadhania <nikunj@linux.vnet.ibm.com>,
Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] [PATCH 0/2] vfio: Another try to fix ROM BAR endianness
Date: Fri, 12 Sep 2014 11:30:01 +1000 [thread overview]
Message-ID: <54124C99.8040504@ozlabs.ru> (raw)
In-Reply-To: <1410470418.2982.354.camel@ul30vt.home>
On 09/12/2014 07:20 AM, Alex Williamson wrote:
> On Tue, 2014-09-09 at 21:34 +1000, Alexey Kardashevskiy wrote:
>> I did some tests on LE/BE guest/host combinations and came up with
>> these 2 patches. Please comment. Thanks.
>
> Have you tried BE guest/LE host?
Yes.
> IIRC, the g3beige tcg guest on x86
> host used to work with a vfio-pci NIC. The ROM is of course typically
> useless in this mode, but it would be nice to make sure we haven't
> broken BAR access for that combination. Do we have any better BE tcg
> targets with PCI support these days? Thanks,
pseries? PPC64 TCG can do VFIO.
--
Alexey
next prev parent reply other threads:[~2014-09-12 1:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-09 11:34 [Qemu-devel] [PATCH 0/2] vfio: Another try to fix ROM BAR endianness Alexey Kardashevskiy
2014-09-09 11:34 ` [Qemu-devel] [PATCH 1/2] Revert "vfio: Make BARs native endian" Alexey Kardashevskiy
2014-09-11 12:16 ` [Qemu-devel] [Qemu-ppc] " Greg Kurz
2014-09-09 11:34 ` [Qemu-devel] [PATCH 2/2] vfio: make rom read endian sensitive Alexey Kardashevskiy
2014-09-09 21:19 ` [Qemu-devel] [PATCH 0/2] vfio: Another try to fix ROM BAR endianness Alexander Graf
2014-09-11 21:20 ` Alex Williamson
2014-09-12 1:30 ` Alexey Kardashevskiy [this message]
2014-09-18 13:55 ` Alexey Kardashevskiy
2014-09-18 15:02 ` Alex Williamson
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=54124C99.8040504@ozlabs.ru \
--to=aik@ozlabs.ru \
--cc=agraf@suse.de \
--cc=alex.williamson@redhat.com \
--cc=nikunj@linux.vnet.ibm.com \
--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).