From: Hannes Reinecke <hare@suse.de>
To: Alexander Bezzubikov <zuban32s@gmail.com>, qemu-devel@nongnu.org
Cc: jsnow@redhat.com, abezzubikov@ispras.ru
Subject: Re: [Qemu-devel] [PATCH RFC v3 0/5] QEMU ATAPI-SCSI bridge GSoC project
Date: Wed, 19 Aug 2015 13:08:52 +0200 [thread overview]
Message-ID: <55D463C4.9030005@suse.de> (raw)
In-Reply-To: <1439981843-2860-1-git-send-email-abezzubikov@ispras.ru>
On 08/19/2015 12:57 PM, Alexander Bezzubikov wrote:
> This is my QEMU Google Summer of Code project.
> Here I introduce new device - ATAPI-SCSI bridge.
> Its purpose is to unify IDE ATAPI CD-ROM emulation
> with SCSI CD-ROM emulation to reduce code duplication and squash bugs.
> It's purpose is simple - it just forwards ATAPI commands
> to SCSI side for parsing and execution.
>
> Example of using:
> qemu-system-x86_64 \
> -drive if=none,file=<filename>,id=cdrom \
> -drive if=none,id=fake \
> -device ide-bridge,id=bridge,drive=fake \
> -device scsi-cd,drive=cdrom,bus=bridge.0 \
> -hda diskimage \
> -m 1024
>
> Alexander Bezzubikov (5):
> ide: ATAPI-SCSI bridge TypeInfo and init function created
> scsi: SCSIDiskReq declaration moved to header
> ide: necessary checks corrected to treat ATAPI-SCSI bridge as CDROM
> ATAPI-SCSI bridge functions created an can be used by bridge
> ide: ATAPI-SCSI bridge transfer is treated as PIO
>
> hw/ide/Makefile.objs | 2 +-
> hw/ide/atapi.c | 20 ++++++++-
> hw/ide/bridge.c | 114 +++++++++++++++++++++++++++++++++++++++++++++++++
> hw/ide/bridge.h | 10 +++++
> hw/ide/core.c | 28 +++++++-----
> hw/ide/internal.h | 6 ++-
> hw/ide/qdev.c | 43 ++++++++++++++++++-
> hw/scsi/scsi-disk.c | 55 ++++++++++++++++++------
> include/hw/scsi/scsi.h | 16 +++++++
> 9 files changed, 267 insertions(+), 27 deletions(-)
> create mode 100644 hw/ide/bridge.c
> create mode 100644 hw/ide/bridge.h
>
I've just got a minor issue on patch 4/5 (rename cur_req to
scsi_req), other than that the patchset looks good.
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: F. Imendörffer, J. Smithard, J. Guild, D. Upmanyu, G. Norton
HRB 21284 (AG Nürnberg)
prev parent reply other threads:[~2015-08-19 11:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-19 10:57 [Qemu-devel] [PATCH RFC v3 0/5] QEMU ATAPI-SCSI bridge GSoC project Alexander Bezzubikov
2015-08-19 10:57 ` [Qemu-devel] [PATCH RFC v3 1/5] ide: ATAPI-SCSI bridge TypeInfo and init function created Alexander Bezzubikov
2015-08-19 10:57 ` [Qemu-devel] [PATCH RFC v3 2/5] scsi: SCSIDiskReq declaration moved to header Alexander Bezzubikov
2015-08-19 10:57 ` [Qemu-devel] [PATCH RFC v3 3/5] ide: necessary checks corrected to treat ATAPI-SCSI bridge as CDROM Alexander Bezzubikov
2015-08-19 10:57 ` [Qemu-devel] [PATCH RFC v3 4/5] ATAPI-SCSI bridge functions created an can be used by bridge Alexander Bezzubikov
2015-08-19 11:08 ` Hannes Reinecke
2015-08-19 10:57 ` [Qemu-devel] [PATCH RFC v3 5/5] ide: ATAPI-SCSI bridge transfer is treated as PIO Alexander Bezzubikov
2015-08-19 11:08 ` Hannes Reinecke [this message]
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=55D463C4.9030005@suse.de \
--to=hare@suse.de \
--cc=abezzubikov@ispras.ru \
--cc=jsnow@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=zuban32s@gmail.com \
/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).