From mboxrd@z Thu Jan 1 00:00:00 1970 From: Juergen Gross Subject: Re: [PATCH 3/4] docs: add pvscsi.txt Date: Mon, 02 Mar 2015 12:04:03 +0100 Message-ID: <54F443A3.9070806@suse.com> References: <1425291362-30228-1-git-send-email-olaf@aepfle.de> <1425291362-30228-4-git-send-email-olaf@aepfle.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1425291362-30228-4-git-send-email-olaf@aepfle.de> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Olaf Hering , xen-devel@lists.xen.org Cc: Ian Jackson , Tim Deegan , Keir Fraser , Ian Campbell , Jan Beulich List-Id: xen-devel@lists.xenproject.org On 03/02/2015 11:16 AM, Olaf Hering wrote: > Signed-off-by: Olaf Hering > Cc: Ian Campbell > Cc: Ian Jackson > Cc: Jan Beulich > Cc: Keir Fraser > Cc: Tim Deegan > --- > docs/misc/pvscsi.txt | 147 +++++++++++++++++++++++++++++++++++++++++++++++++++ > 1 file changed, 147 insertions(+) > > diff --git a/docs/misc/pvscsi.txt b/docs/misc/pvscsi.txt > new file mode 100644 > index 0000000..2af050f > --- /dev/null > +++ b/docs/misc/pvscsi.txt > @@ -0,0 +1,147 @@ > +. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . > +PVSCSI > + > +== Overview == > + > +PVSCSI allows to assing a "physical" SCSI device from dom0 to a domU. The device > +is not limited to be a native SCSI device. Everything visible as SCSI device in > +dom0 can be used. Currently PVSCSI is only available in Linux dom0 and domU. > + > +== TODO === > + > +How to do live migration? > + - pdev will likely be evaluated again on the target host if it came from > + domU.cfg. But what about pdev from 'xl scsi-attach pdev vdev'? Its required > + to adjust h:c:t:l on the target host. Use WWN notation? :-) This was one of the reason the backend should support it. > + > +Implement checks for duplicate pdev assignments? > + - Not sure if SCSI devices can be shared. Will the state be consistent during > + concurrent access? Should the host admin assume cooperative access from > + multiple domUs? SCSI does support device sharing. That's the reason for the existence of SCSI commands like "reserve" and "release". Juergen