Displaying 20 results from an estimated 50000 matches similar to: "[PATCH 3/4] [LINUX] add scsi backend and frontend RING interface"
2008 Jul 03
3
[PATCH 2/4] pvSCSI : Fix many points of backend/frontend driver
Please refer following Mr. Steven''s mail posted on June 24th.
Message-ID: <20080624131313.GB18379@weybridge.uk.xensource.com>
Message-ID: <20080624131256.GA18379@weybridge.uk.xensource.com>
Signed-off-by: Tomonari Horikoshi <t.horikoshi@jp.fujitsu.com>
Signed-off-by: Jun Kamada <kama@jp.fujitsu.com>
-----
Jun Kamada
2007 Oct 19
0
[PATCH 5/5] pvSCSI (SCSI pass through) driver
This patch is for modifying xend in order to use pvscsi driver.
(attach/detach HBA, etc.)
Signed-off-by: Tomonari Horikoshi <t.horikoshi@jp.fujitsu.com>
Signed-off-by: Tsunehisa Doi <Doi.Tsunehisa@jp.fujitsu.com>
Signed-off-by: Jun Kamada <kama@jp.fujitsu.com>
Signed-off-by: Akira Hayakawa <hayakawa.akira@jp.fujitsu.com>
-----
Jun Kamada
2007 Oct 19
0
[PATCH 2/5] pvSCSI (SCSI pass through) driver
This patch is for backend driver.
Signed-off-by: Tomonari Horikoshi <t.horikoshi@jp.fujitsu.com>
Signed-off-by: Tsunehisa Doi <Doi.Tsunehisa@jp.fujitsu.com>
Signed-off-by: Jun Kamada <kama@jp.fujitsu.com>
Signed-off-by: Akira Hayakawa <hayakawa.akira@jp.fujitsu.com>
-----
Jun Kamada
_______________________________________________
Xen-devel mailing list
2007 Oct 19
0
[PATCH 3/5] pvSCSI (SCSI pass through) driver
This patch is for Makefile and Kconfig file for scsifront and scsiback
driver.
Signed-off-by: Tomonari Horikoshi <t.horikoshi@jp.fujitsu.com>
Signed-off-by: Tsunehisa Doi <Doi.Tsunehisa@jp.fujitsu.com>
Signed-off-by: Jun Kamada <kama@jp.fujitsu.com>
Signed-off-by: Akira Hayakawa <hayakawa.akira@jp.fujitsu.com>
-----
Jun Kamada
2008 Jul 03
3
[PATCH 1/4] pvSCSI : Add white list to SCSI command emulation
Add "white list" control to SCSI command emulation. Current setting
allows following mandatory and safe commands.
TEST UNIT READY
REZERO UNIT
REQUEST SENSE
FORMAT UNIT
READ BLOCK LIMITS
READ(06)
WRITE(06)
WRITE FILEMARKS
SPACE
INQUIRY
ERASE
MODE SENSE(06)
SEND DIAGNOSTIC
READ CAPACITY
READ(10)
WRITE(10)
REPORT LUN
Signed-off-by: Tomonari Horikoshi <t.horikoshi@jp.fujitsu.com>
2007 May 16
5
[RFC] pv-scsi driver (scsiback/scsifront)
Hi all.
We developped a pv-scsi driver that we refered Fujita-san''s scsi-driver
and blkback.
(see, http://www.xensource.com/files/xensummit_4/Xen_Summit_8_Matsumoto.pdf)
The pv-scsi driver''s feature is as follow:
* Guest has dedicated SCSI-HBAs of Dom0.
* Guest can send scsi_cdb to the HBAs.
* Guest recognises the HBAs from hostno of xenstore.
Currentlly, We are
2008 Feb 18
0
[Patch 2/7] pvSCSI driver
Patch in order to make pvSCSI work on HVM.
Signed-off-by: Tomonari Horikoshi <t.horikoshi@jp.fujitsu.com>
Signed-off-by: Jun Kamada <kama@jp.fujitsu.com>
Signed-off-by: Akira Hayakawa <hayakawa.akira@jp.fujitsu.com>
-----
Jun Kamada
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
2007 Nov 06
0
[PATCH] [PV-ON-HVM] Fix evtchn of unbind_from_irqhandler()
Hi All,
When xm block-detach command was done on PV-ON-HVM,
the response of other disks was lost.
It is because a wrong event channel was invalidated when detaching it.
Not the evtchn number but the irq number is invalidated specifying it.
Signed-off-by: Takanori Kasai <kasai.takanori@jp.fujitsu.com>
Signed-off-by: Tomonari Horikoshi <t.horikoshi@jp.fujitsu.com>
Signed-off-by:
2007 Oct 15
2
[PATCH] [IOEMU] Allow blktap to be able to be booted as systemvolume for PV-on-HVM(TAKE 3)
Hi All,
I sent the patch to make blktap work with PV-on-HVM.
I corrected the part that had been pointed out in the Xen community.
・All xvdN disk is looked like hdN.
・All tap disks are checked.(tap:aio, tap:sync, tap:vmdk, etc.)
We cannot use blktap for the volume of the system with PV-on-HVM
and are embarrassed.
Could you apply this patch? Or, please give the comment to me.
Signed-off-by:
2008 Feb 18
14
[Patch 3/7] pvSCSI driver
Add vscsiif.h
Signed-off-by: Tomonari Horikoshi <t.horikoshi@jp.fujitsu.com>
Signed-off-by: Jun Kamada <kama@jp.fujitsu.com>
Signed-off-by: Akira Hayakawa <hayakawa.akira@jp.fujitsu.com>
-----
Jun Kamada
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
2008 Jun 19
0
[PATCH] ia64/xen: introduce definitions necessary for ia64/xen hypercalls.
import include/asm-ia64/xen/interface.h to introduce introduce
definitions necessary for ia64/xen hypercalls.
They are basic structures to communicate with xen hypervisor and
will be used later.
Cc: Robin Holt <holt at sgi.com>
Cc: Jeremy Fitzhardinge <jeremy at goop.org>
Signed-off-by: Isaku Yamahata <yamahata at valinux.co.jp>
Cc: "Luck, Tony" <tony.luck at
2008 Jun 19
0
[PATCH] ia64/xen: introduce definitions necessary for ia64/xen hypercalls.
import include/asm-ia64/xen/interface.h to introduce introduce
definitions necessary for ia64/xen hypercalls.
They are basic structures to communicate with xen hypervisor and
will be used later.
Cc: Robin Holt <holt at sgi.com>
Cc: Jeremy Fitzhardinge <jeremy at goop.org>
Signed-off-by: Isaku Yamahata <yamahata at valinux.co.jp>
Cc: "Luck, Tony" <tony.luck at
2006 Aug 02
0
[PATCH 0/6] SCSI frontend and backend drivers
This patchset includes an updated version of the SCSI frontend and
backend drivers.
The frontend and backend drivers exchange SCSI RDMA Protocol (SRP)
messages via a ring buffer. The backend driver sends SCSI commands to
the user-space daemon, which performs SCSI commands and I/O
operations. The backend driver uses VM_FOREIGN feature like the blktap
driver for zero-copy of data pages.
Like the
2008 Jul 10
2
Minor synchronisation quibble in scsifront
I''ve been having a look through scsifront again, and I saw this bit:
ring_req->timeout_per_command = (sc->timeout_per_command / HZ);
ring_req->nr_segments = 0;
spin_unlock_irq(host->host_lock);
scsifront_do_request(info);
wait_event_interruptible(info->shadow[ring_req->rqid].wq_reset,
info->shadow[ring_req->rqid].wait_reset);
in
2008 May 30
5
[PATCH 1/4] pvSCSI driver
pvSCSI backend driver
Signed-off-by: Tomonari Horikoshi <t.horikoshi@jp.fujitsu.com>
Signed-off-by: Jun Kamada <kama@jp.fujitsu.com>
-----
Jun Kamada
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
2009 Mar 23
0
[PATCH 2/2] PVUSB: correct the license headers (frontend part)
This patch correct the license headers of the PVUSB frontend driver.
Signed-off-by: Noboru Iwamatsu <n_iwamatsu@jp.fujitsu.com>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
2010 Oct 27
1
[Startup] Java Backend and Rails Frontend
I have a startup considering building a Java backend and a Rails
frontend. The Java backend will take care of creating a caching layer
for the database and offer other additional services. The Rails
frontend will mostly be for creating the webapp and monitoring tools.
What startups/companies out there are using this kind of setup? What
are some gotchas in terms of development speed, deployment,
2007 Nov 28
8
SCSI passthrough using /dev/sgX
Is anyone working on SCSI passthrough using the ''SCSI Generic'' support
under Linux, eg /dev/sgX? This is how VMWare allows a VM to use SCSI
devices.
Thanks
James
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
2009 Aug 06
0
[LLVMdev] i128 backend or frontend lowering
Hello, Andrew
> Is the backend the best place to do this or should I attempt to make
> llvm-gcc not generate i128 in the first place?
It depends whether i128 is a native type for alpha, or not. If it's
not - frontend should not generate it. If it's native type then it
might be useful just to declare new regclass with virtual 'wide'
registers consist of register pairs and
2009 Aug 06
4
[LLVMdev] i128 backend or frontend lowering
I am seeing i128 from llvm-gcc on Alpha. I know the calling
convention for them, they are split into two registers, but I don't
know if that should be handled in the frontend or the backend. I
would just as soon do it in the backend, but I didn't see any support
in the new calling convention work for automatically splitting an
argument into multiple registers.
Is the backend the best