From: Juergen Gross <jgross@suse.com>
To: David Vrabel <david.vrabel@citrix.com>,
jgross@suse.com, JBottomley@parallels.com,
linux-scsi@vger.kernel.org, xen-devel@lists.xen.org
Subject: Re: [Xen-devel] [PATCH 2/4] Introduce xen-scsifront module
Date: Mon, 30 Jun 2014 15:51:03 +0200 [thread overview]
Message-ID: <53B16B47.4050102@suse.com> (raw)
In-Reply-To: <53B167B5.7070104@citrix.com>
On 06/30/2014 03:35 PM, David Vrabel wrote:
> On 27/06/14 15:34, jgross@suse.com wrote:
>>
>> +/* .resume = scsifront_resume, */
>
> Following on from the recent discussion on migration with front/backends
> I thought I'd review how this new driver does it.
"New" is an attribute I wouldn't use in this case. The driver was
introduced in 2008, this is just a rework to be able to put it in
the upstream kernel.
> Is there an expectation that a VM with a PV scsi device cannot be
> restored or migrated?
It has been so in the past.
To change this is on my todo list, but that's not top priority.
Juergen
next prev parent reply other threads:[~2014-06-30 13:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-27 14:34 Add XEN pvSCSI support jgross
2014-06-27 14:34 ` [PATCH 1/4] Add XEN pvSCSI protocol description jgross
2014-06-27 17:11 ` [Xen-devel] " Konrad Rzeszutek Wilk
2014-06-30 8:26 ` Juergen Gross
2014-06-30 11:02 ` Jan Beulich
2014-06-30 11:18 ` Juergen Gross
2014-06-30 11:29 ` Jan Beulich
2014-06-27 14:34 ` [PATCH 2/4] Introduce xen-scsifront module jgross
2014-06-30 13:35 ` [Xen-devel] " David Vrabel
2014-06-30 13:51 ` Juergen Gross [this message]
2014-06-27 14:34 ` [PATCH 3/4] Introduce XEN scsiback module jgross
2014-06-28 18:09 ` Christoph Hellwig
2014-07-11 8:57 ` Juergen Gross
2014-07-11 9:04 ` Christoph Hellwig
2014-06-27 14:34 ` [PATCH 4/4] add xen pvscsi maintainer jgross
2014-06-27 17:13 ` Konrad Rzeszutek Wilk
2014-06-27 17:45 ` Add XEN pvSCSI support Pasi Kärkkäinen
2014-06-27 17:51 ` [Xen-devel] " Pasi Kärkkäinen
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=53B16B47.4050102@suse.com \
--to=jgross@suse.com \
--cc=JBottomley@parallels.com \
--cc=david.vrabel@citrix.com \
--cc=linux-scsi@vger.kernel.org \
--cc=xen-devel@lists.xen.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