From: Auger Eric <eric.auger@redhat.com>
To: Andrew Jones <drjones@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [Qemu-devel] Do we need a "virt-2.10" machine type before the 2.10 release?
Date: Mon, 7 Aug 2017 09:10:27 +0200 [thread overview]
Message-ID: <5871a85b-4d73-78f2-1aad-45e978ef6051@redhat.com> (raw)
In-Reply-To: <20170807070622.yenthqql6rgdhm77@kamzik.brq.redhat.com>
Hi Drew,
On 07/08/2017 09:06, Andrew Jones wrote:
> On Fri, Aug 04, 2017 at 06:42:54PM +0100, Peter Maydell wrote:
>> Hi; I noticed today that the virt board doesn't have a virt-2.10
>> machine type defined. Do we need to add it before release?
>>
>> (I don't know if there have in fact been any changes between
>> 2.9 and 2.10 that would be compatibility issues.)
>>
>> thanks
>> -- PMM
>>
>
> Yes, we should have separately posted that to make sure it
> got in. Eric posted it, but as part of an RFC series:
>
> https://lists.gnu.org/archive/html/qemu-devel/2017-08/msg00045.html
>
> Eric, would you like to post a separate patch for the 2.10
> machine type that doesn't include no_iommu?
Yes I can send it. However is it really mandated as I don't think we
have changes between 2.9 and 2.10?
Thanks
Eric
>
> Thanks,
> drew
>
prev parent reply other threads:[~2017-08-07 7:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-04 17:42 [Qemu-devel] Do we need a "virt-2.10" machine type before the 2.10 release? Peter Maydell
2017-08-04 17:48 ` Dr. David Alan Gilbert
2017-08-04 17:51 ` Peter Maydell
2017-08-06 21:20 ` Paolo Bonzini
2017-08-07 7:06 ` Andrew Jones
2017-08-07 7:10 ` Auger Eric [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=5871a85b-4d73-78f2-1aad-45e978ef6051@redhat.com \
--to=eric.auger@redhat.com \
--cc=dgilbert@redhat.com \
--cc=drjones@redhat.com \
--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).