From: Eric Auger <eric.auger@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: b.reynal@virtualopensystems.com,
Patch Tracking <patches@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>,
Alex Williamson <alex.williamson@redhat.com>,
eric.auger@st.com, Christoffer Dall <christoffer.dall@linaro.org>
Subject: Re: [Qemu-devel] [PATCH v17] hw/arm/sysbus-fdt: enable vfio-calxeda-xgmac dynamic instantiation
Date: Mon, 22 Jun 2015 09:47:13 +0200 [thread overview]
Message-ID: <5587BD81.1010408@linaro.org> (raw)
In-Reply-To: <CAFEAcA8vQywoDfD4+4RZ1H2zifveWMYFabmLH4SmD-yDT2WKvg@mail.gmail.com>
On 06/18/2015 10:27 PM, Peter Maydell wrote:
> On 16 June 2015 at 13:11, Eric Auger <eric.auger@linaro.org> wrote:
>> Hi Peter,
>> On 06/16/2015 01:59 PM, Peter Maydell wrote:
>>> This was part of a series before -- is it a standalone
>>> patch now? What's the relationship with the other patches?
>>
>> This patch makes possible to instantiate the VFIO Calxeda xgmac device
>> which is already in the master. The rest of the series enables irqfd
>> usage by the base VFIO device so to me it is independent. Currently
>> eventfds are handled on user-side, which is particularly inefficient but
>> functional.
>>
>> Let me know if you prefer I resend the whole series.
>
> OK, if it stands on its own I can apply this to target-arm.next.
> Please update the changelog wiki page with something appropriate
> about this new feature.
Hi Peter,
thanks for the pull. I don't have any wiki account yet. Can anyone
create an account for me?
Best Regards
Eric
>
> -- PMM
>
prev parent reply other threads:[~2015-06-22 7:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-16 11:58 [Qemu-devel] [PATCH v17] hw/arm/sysbus-fdt: enable vfio-calxeda-xgmac dynamic instantiation Eric Auger
2015-06-16 11:59 ` Peter Maydell
2015-06-16 12:11 ` Eric Auger
2015-06-18 20:27 ` Peter Maydell
2015-06-22 7:47 ` Eric Auger [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=5587BD81.1010408@linaro.org \
--to=eric.auger@linaro.org \
--cc=alex.williamson@redhat.com \
--cc=b.reynal@virtualopensystems.com \
--cc=christoffer.dall@linaro.org \
--cc=eric.auger@st.com \
--cc=patches@linaro.org \
--cc=peter.maydell@linaro.org \
--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).