qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: adq <adq@lidskialf.net>
To: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
Cc: stefanha@gmail.com, kraxel@redhat.com,
	Christoph Hellwig <hch@lst.de>,
	qemu-devel@nongnu.org, Hannes Reinecke <hare@suse.de>
Subject: Re: [Qemu-devel] [PATCH 12/16] scsi-generic: use plain ioctl
Date: Sat, 20 Nov 2010 13:16:20 +0000	[thread overview]
Message-ID: <AANLkTi=xuwW8mc2EXy4=_FMHT6buCdCvMDFMwgHeHQES@mail.gmail.com> (raw)
In-Reply-To: <1290241380.28657.102.camel@haakon2.linux-iscsi.org>

On 20 November 2010 08:23, Nicholas A. Bellinger <nab@linux-iscsi.org> wrote:
> On Sat, 2010-11-20 at 01:25 +0000, adq wrote:
>> On 20 November 2010 00:41, Nicholas A. Bellinger <nab@linux-iscsi.org> wrote:
>> > On Fri, 2010-11-19 at 19:39 +0100, Christoph Hellwig wrote:
>> >> On Thu, Nov 18, 2010 at 03:47:36PM +0100, Hannes Reinecke wrote:
>> >> >
>> >> > aio_ioctl is emulated anyway and currently broken.
>> >>
>> >> What's broken about it currently?
>> >
>> > Mmmmmm, I do not recall this being broken in the first place..?  There
>> > was a single issue with megasas+bdrv_aio_ioctl() with WinXP (that did
>> > not appear with lsi53c895a) that was mentioned on the list earlier in
>> > the year that required a patch to use bdev_ioctl(), but last I recall
>> > Hannes had already fixed this in recent megasas.c code w/ 32-bit MSFT
>> > guests.  Also, this is what I have been with scsi_generic.c and
>> > scsi_bsg.c into TCM_loop in my v0.12.5 megasas tree, and I am not
>> > observing any obvious issues with AIO IOCTLs for SG_IO/BSG into Linux
>> > guests.
>> >
>> > I will give AIO IOCTL ops a run with these on v2.6.37-rc2 lock-less KVM
>> > host mode <-> TCM_Loop to verify against the v0.12.5 megasas tree.
>>
>> Could this AIO ioctl breakage perhaps be the one I fixed here?
>> http://web.archiveorange.com/archive/v/1XS1vROmfC7dN9wYxsmt
>>
>> The patch is defintely in the latest git... it works fine for me with
>> my scsi-generic MMC command patches.
>>
>
> Interesting read, and thanks for the heads up on this bit..   I do not
> personally recall running into any issues with TYPE_DISK w/ lsi53c895a
> and AIO SG_IO into WinXP guests on v0.12.5 code.   After a quick double
> check in the v0.12.5 megasas tree, the proper get_async_context_id() is
> still present:
>
> http://git.kernel.org/?p=virt/kvm/nab/qemu-kvm.git;a=blob;f=posix-aio-compat.c;h=ccdbf9a16d0ef1d7e57c87dbe43f318d4c7a5967;hb=HEAD#l560
>
> So it appears this acb->async_context_id was incorrectly dropped during
> v0.13 development, and with your fix commited into v0.13 mainline code
> that Hannes should be able to safetly drop this the megasas series,
> yes..?
>
> Thank you for your comments!

No problem. Oh, that bug was /definitely/ in the released 0.12.x
series code; I spotted it when trying to get scsi-generic to work on
arch linux, which was using 0.12.x.

  reply	other threads:[~2010-11-20 13:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-18 14:47 [Qemu-devel] [PATCH 12/16] scsi-generic: use plain ioctl Hannes Reinecke
2010-11-19 18:39 ` Christoph Hellwig
2010-11-20  0:41   ` Nicholas A. Bellinger
2010-11-20  1:25     ` adq
2010-11-20  8:23       ` Nicholas A. Bellinger
2010-11-20 13:16         ` adq [this message]
2010-11-22  7:21       ` Hannes Reinecke

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='AANLkTi=xuwW8mc2EXy4=_FMHT6buCdCvMDFMwgHeHQES@mail.gmail.com' \
    --to=adq@lidskialf.net \
    --cc=hare@suse.de \
    --cc=hch@lst.de \
    --cc=kraxel@redhat.com \
    --cc=nab@linux-iscsi.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@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).