All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Jackson <ian.jackson@eu.citrix.com>
To: Olaf Hering <olaf@aepfle.de>
Cc: xen-devel@lists.xenproject.org, Olaf Hering <ohering@suse.de>
Subject: Re: [PATCH qemu-xen-traditional 1/2] xen_platform: unplug also SCSI disks [and 1 more messages]
Date: Mon, 9 Jan 2017 14:34:06 +0000	[thread overview]
Message-ID: <22643.40798.969287.384827@mariner.uk.xensource.com> (raw)
In-Reply-To: <20161124201130.16558-2-olaf@aepfle.de>, <20161124201130.16558-3-olaf@aepfle.de>

Olaf Hering writes ("[PATCH qemu-xen-traditional 1/2] xen_platform: unplug also SCSI disks"):
> From: Olaf Hering <ohering@suse.de>
> 
> 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.

qemu-xen-traditional is in the deep freeze.  I'm only fixes for quite
serious problems (such as security problems).

> Impact of the change for classic and pvops based guest kernels:

While I think this change has a risk of breaking things, and certainly
wouldn't warrant backporting to earlier Xen releases, I think there is
an arguable case for this patch.  At the very least it only affects
users with scsi disks.

That the patch has been in use in SUSE for a long time is also a
helpful datapoint.

I am inclined to accept this patch but would welcome opinions from
others.  Olaf, if no-one replies, please ping me about this again, and
I will apply it.

Olaf Hering writes ("[PATCH qemu-xen-traditional 2/2] xen_platform: SUSE xenlinux unplug for emulated PCI"):
> From: Olaf Hering <ohering@suse.de>
> 
> Implement SUSE specific unplug protocol for emulated PCI devices
> in PVonHVM guests. Its a simple 'outl(1, (ioaddr + 4));'.
> This protocol was implemented and used since Xen 3.0.4.
> It is used in all SUSE/SLES/openSUSE releases up to SLES11SP3 and
> openSUSE 12.3.
> In addition old (pre-2011) VMDP versions are handled as well.

On the other hand, I am very reluctant to apply this.

I don't see a good reason for SUSE to have a custom unplug protocol.
Why can't your guests use the standard one ?  Why haven't they been
updated to use the standard one some time in the last ?5-10 years ?

We had a similar question about certain Citrix XenServer behaviours.
I forget the details.  But if I remember that was also a case where a
downstream had invented a private variant of an upstream protocol,
failed to coordinate with upstream, and simply shipped a revised
protocol.  Again there we resisted incorporation of ad-hoc protocols.

Sorry.

Thanks,
Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2017-01-09 14:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-24 20:11 [PATCH qemu-xen-traditional 0/2] Xen HVM unplug changes Olaf Hering
2016-11-24 20:11 ` [PATCH qemu-xen-traditional 1/2] xen_platform: unplug also SCSI disks Olaf Hering
2017-01-09 14:34   ` Ian Jackson [this message]
2017-01-09 16:39     ` [PATCH qemu-xen-traditional 1/2] xen_platform: unplug also SCSI disks [and 1 more messages] Olaf Hering
2017-01-10 10:34       ` George Dunlap
2017-01-31 17:14         ` Olaf Hering
2017-01-31 17:32           ` Ian Jackson
2017-01-31 17:44             ` Olaf Hering
2016-11-24 20:11 ` [PATCH qemu-xen-traditional 2/2] xen_platform: SUSE xenlinux unplug for emulated PCI Olaf Hering
2017-01-09 11:23 ` [PATCH qemu-xen-traditional 0/2] Xen HVM unplug changes Olaf Hering
2017-01-09 14:26   ` Ian Jackson

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=22643.40798.969287.384827@mariner.uk.xensource.com \
    --to=ian.jackson@eu.citrix.com \
    --cc=ohering@suse.de \
    --cc=olaf@aepfle.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.