From: Olaf Hering <olaf@aepfle.de>
To: Stefano Stabellini <sstabellini@kernel.org>,
Anthony Perard <anthony.perard@citrix.com>
Cc: xen-devel@lists.xenproject.org
Subject: Re: [PATCH v3 1/2] xen_platform: unplug also SCSI disks
Date: Thu, 24 Nov 2016 11:59:06 +0100 [thread overview]
Message-ID: <20161124105855.GA22790@aepfle.de> (raw)
In-Reply-To: <20161021123707.18302-2-olaf@aepfle.de>
[-- Attachment #1.1: Type: text/plain, Size: 671 bytes --]
On Fri, Oct 21, Olaf Hering wrote:
> Using 'vdev=sd[a-o]' will create an emulated LSI controller, which can
> be used by the emulated BIOS to boot from disk. If the HVM domU has also
> PV driver the disk may appear twice in the guest. To avoid this an
> unplug of the emulated hardware is needed, similar to what is done for
> IDE and NIC drivers already.
How are these patches supposed to find their way into
qemu-xen.git#staging? Do I have to wait until #staging gets updated to
qemu-2.8+ at some point, or would you please cherry-pick these two commits:
3513201 xen_platform: SUSE xenlinux unplug for emulated PCI
78f6689 xen_platform: unplug also SCSI disks
Olaf
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 163 bytes --]
[-- Attachment #2: Type: text/plain, Size: 127 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-11-24 10:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-21 12:37 [PATCH v3 0/2] Xen HVM unplug changes Olaf Hering
2016-10-21 12:37 ` [PATCH v3 1/2] xen_platform: unplug also SCSI disks Olaf Hering
2016-10-21 19:54 ` Stefano Stabellini
2016-11-24 10:59 ` Olaf Hering [this message]
2016-11-28 18:28 ` Stefano Stabellini
2016-11-29 4:18 ` Wei Liu
2016-11-29 14:41 ` Olaf Hering
2016-10-21 12:37 ` [PATCH v3 2/2] xen_platform: SUSE xenlinux unplug for emulated PCI Olaf Hering
2016-10-21 19:55 ` Stefano Stabellini
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=20161124105855.GA22790@aepfle.de \
--to=olaf@aepfle.de \
--cc=anthony.perard@citrix.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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).