From: Paolo Bonzini <pbonzini@redhat.com>
To: Igor Mammedov <imammedo@redhat.com>, Peter Xu <peterx@redhat.com>
Cc: qemu-devel@nongnu.org, peter.maydell@linaro.org, mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH v3] x86: ioapic: add support for explicit EOI
Date: Mon, 1 Aug 2016 16:45:16 +0200 [thread overview]
Message-ID: <394b8f02-d91e-3fc8-9522-7ecccd464647@redhat.com> (raw)
In-Reply-To: <20160801164326.7d9b962f@nial.brq.redhat.com>
On 01/08/2016 16:43, Igor Mammedov wrote:
> > To be compatible with old systems, 0x11 will still be the default IOAPIC
> > version. Here 0x11 and 0x20 are the only versions to be supported.
>
> Is there a reason not to default to 0x20 for new machine types and
> set 2.6 and older machine types to 0x11?
See discussion in v2. It's just for safety, what you just said is
indeed the plan for 2.8. This patch already provides the necessary
infrastructure.
Paolo
next prev parent reply other threads:[~2016-08-01 14:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-01 13:59 [Qemu-devel] [PATCH v3] x86: ioapic: add support for explicit EOI Peter Xu
2016-08-01 14:43 ` Igor Mammedov
2016-08-01 14:45 ` Paolo Bonzini [this message]
2016-08-02 2:50 ` Peter Xu
2016-08-01 14:56 ` Paolo Bonzini
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=394b8f02-d91e-3fc8-9522-7ecccd464647@redhat.com \
--to=pbonzini@redhat.com \
--cc=imammedo@redhat.com \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=peterx@redhat.com \
--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).