From: "Dr. David Alan Gilbert (git)" <dgilbert@redhat.com>
To: qemu-devel@nongnu.org, pbonzini@redhat.com, eduardo@habkost.net,
mst@redhat.com, thuth@redhat.com, berrange@redhat.com,
quintela@redhat.com
Subject: [PATCH 0/3] x86: Switch over to q35 as the default machine type
Date: Tue, 15 Feb 2022 16:25:34 +0000 [thread overview]
Message-ID: <20220215162537.605030-5-dgilbert@redhat.com> (raw)
In-Reply-To: <20220215162537.605030-1-dgilbert@redhat.com>
From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
We've been using q35 heavily for a while now and it generally works
quite nicely; downstream in RH we prefer it as our default, and I wanted
to see what people think of making it the default.
The only pain really is that it requires some more setup for hotplug;
so for now I've forced hotplug tests to stay on i440fx aka pc.
Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Dr. David Alan Gilbert (3):
tests/x86: Use 'pc' machine type for old hardware tests
tests/x86: Use 'pc' machine type for hotplug tests
x86: Switch to q35 as the default machine type
hw/i386/pc_piix.c | 12 +-----------
hw/i386/pc_q35.c | 2 ++
tests/qtest/device-plug-test.c | 20 +++++++++++++++++--
tests/qtest/drive_del-test.c | 35 +++++++++++++++++++++++++++++-----
tests/qtest/fdc-test.c | 2 +-
tests/qtest/hd-geo-test.c | 16 +++++++++++-----
tests/qtest/i440fx-test.c | 2 +-
tests/qtest/ide-test.c | 3 ++-
tests/qtest/ivshmem-test.c | 7 ++++++-
9 files changed, 72 insertions(+), 27 deletions(-)
--
2.35.1
next prev parent reply other threads:[~2022-02-15 16:31 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 16:25 [PATCH 0/3] x86: Switch over to q35 as the default machine type Dr. David Alan Gilbert (git)
2022-02-15 16:25 ` [PATCH 1/3] tests/x86: Use 'pc' machine type for old hardware tests Dr. David Alan Gilbert (git)
2022-02-17 8:04 ` Thomas Huth
2022-02-17 8:18 ` Michael S. Tsirkin
2022-02-15 16:25 ` [PATCH 2/3] tests/x86: Use 'pc' machine type for hotplug tests Dr. David Alan Gilbert (git)
2022-02-17 8:09 ` Thomas Huth
2022-02-17 8:18 ` Michael S. Tsirkin
2022-02-15 16:25 ` [PATCH 3/3] x86: Switch to q35 as the default machine type Dr. David Alan Gilbert (git)
2022-02-15 18:13 ` Daniel P. Berrangé
2022-02-15 18:29 ` Dr. David Alan Gilbert
2022-02-16 10:58 ` Gerd Hoffmann
2022-02-16 11:01 ` Dr. David Alan Gilbert
2022-02-16 11:23 ` Daniel P. Berrangé
2022-02-16 11:24 ` Thomas Huth
2022-02-16 17:40 ` Dr. David Alan Gilbert
2022-02-16 17:48 ` Daniel P. Berrangé
2022-02-16 17:57 ` Dr. David Alan Gilbert
2022-02-17 7:46 ` Thomas Huth
2022-02-17 7:52 ` Michael S. Tsirkin
2022-02-17 9:29 ` Daniel P. Berrangé
2022-02-17 9:43 ` Dr. David Alan Gilbert
2022-02-17 7:57 ` Thomas Huth
2022-02-17 8:08 ` Gerd Hoffmann
2022-02-17 8:17 ` Michael S. Tsirkin
2022-02-17 9:16 ` Daniel P. Berrangé
2022-02-17 9:35 ` Igor Mammedov
2022-02-17 9:19 ` Kashyap Chamarthy
2022-02-15 16:25 ` Dr. David Alan Gilbert (git) [this message]
2022-02-15 16:25 ` [PATCH 1/3] tests/x86: Use 'pc' machine type for old hardware tests Dr. David Alan Gilbert (git)
2022-02-15 16:25 ` [PATCH 2/3] tests/x86: Use 'pc' machine type for hotplug tests Dr. David Alan Gilbert (git)
2022-02-15 16:25 ` [PATCH 3/3] x86: Switch to q35 as the default machine type Dr. David Alan Gilbert (git)
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=20220215162537.605030-5-dgilbert@redhat.com \
--to=dgilbert@redhat.com \
--cc=berrange@redhat.com \
--cc=eduardo@habkost.net \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=thuth@redhat.com \
/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).