From: Olaf Hering <olaf@aepfle.de>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Eduardo Habkost <ehabkost@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Paul Durrant <paul@xen.org>,
"open list:All patches CC here" <qemu-devel@nongnu.org>,
Anthony Perard <anthony.perard@citrix.com>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [PATCH v2] hw/i386: disable smbus migration for xenfv
Date: Wed, 19 Feb 2020 15:14:59 +0100 [thread overview]
Message-ID: <20200219151459.5a6b9690.olaf@aepfle.de> (raw)
In-Reply-To: <20200219123530.11064fc5.olaf@aepfle.de>
[-- Attachment #1: Type: text/plain, Size: 533 bytes --]
Am Wed, 19 Feb 2020 12:35:30 +0100
schrieb Olaf Hering <olaf@aepfle.de>:
> Is any of the things done by pc_i440fx_5_0_machine_options and
> pc_i440fx_machine_options a desired, or even breaking, change for the
> current result of pc_xen_hvm_init?
I tried to follow a few of the initialized members:
default_nic_model, perhaps the involved code paths are not called, so the NULL pointer does not matter.
pvh_enabled, does this mean the PVH domU type? If yes, this would be lost when xenfv is locked at v3.1.
Olaf
[-- Attachment #2: Digitale Signatur von OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-02-19 14:18 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-13 17:45 [PATCH v1] hw/i386: disable smbus migration for xenpv Olaf Hering
2020-01-13 17:46 ` [PATCH v1] hw/i386: disable smbus migration for xenfv Olaf Hering
2020-01-15 13:51 ` [PATCH v1] hw/i386: disable smbus migration for xenpv Michael S. Tsirkin
2020-01-16 18:03 ` [PATCH v2] hw/i386: disable smbus migration for xenfv Olaf Hering
2020-01-16 18:26 ` Paolo Bonzini
2020-01-16 18:33 ` Olaf Hering
2020-01-16 18:50 ` Paolo Bonzini
2020-01-17 9:22 ` Olaf Hering
2020-01-17 10:27 ` Paolo Bonzini
2020-01-17 13:06 ` Olaf Hering
2020-01-20 11:18 ` Paul Durrant
2020-01-27 9:09 ` Olaf Hering
2020-02-18 17:27 ` Olaf Hering
2020-02-18 17:37 ` Paolo Bonzini
2020-02-18 18:30 ` Olaf Hering
2020-02-18 19:44 ` Olaf Hering
2020-02-19 8:05 ` Paolo Bonzini
2020-02-19 8:13 ` Olaf Hering
2020-01-27 9:35 ` Paolo Bonzini
2020-01-27 13:26 ` Olaf Hering
2020-01-27 18:21 ` Paolo Bonzini
2020-02-19 11:35 ` Olaf Hering
2020-02-19 14:14 ` Olaf Hering [this message]
2020-02-20 10:50 ` Paolo Bonzini
2020-03-25 6:47 ` [PATCH v3] piix: fix xenfv regression, add compat machine xenfv-qemu4 Olaf Hering
2020-03-25 7:11 ` no-reply
2020-03-25 7:25 ` no-reply
2020-03-25 15:39 ` Paolo Bonzini
2020-03-25 15:45 ` Olaf Hering
2020-03-25 17:06 ` Paolo Bonzini
2020-03-27 15:19 ` Olaf Hering
2020-03-27 15:18 ` [PATCH v4] " Olaf Hering
2020-03-27 15:45 ` no-reply
2020-03-27 15:59 ` Paolo Bonzini
2020-03-28 7:09 ` Olaf Hering
2020-03-28 8:56 ` Paolo Bonzini
2020-04-06 16:00 ` Paolo Bonzini
2020-04-06 16:11 ` Olaf Hering
2020-03-27 16:01 ` no-reply
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=20200219151459.5a6b9690.olaf@aepfle.de \
--to=olaf@aepfle.de \
--cc=anthony.perard@citrix.com \
--cc=ehabkost@redhat.com \
--cc=mst@redhat.com \
--cc=paul@xen.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=sstabellini@kernel.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).