From: Pezza <mario.beccia@tiscali.it>
To: xen-devel@lists.xensource.com
Subject: Re: writing PV block drivers for Windows
Date: Fri, 19 Oct 2007 17:50:53 -0700 (PDT) [thread overview]
Message-ID: <13305487.post@talk.nabble.com> (raw)
In-Reply-To: <AEC6C66638C05B468B556EA548C1A77D01249AB9@trantor>
James,
I'd be pretty much interested in the evolution this thing had (1 month has
passed...).
Have you got anything functional? Do you need any help with it (I'd be
extremely interested in this)?
James Harper wrote:
>
> I'm now at the stage where I can think about writing some PV block
> drivers for Windows. I have working event channel and xen store
> subsystems (but they'll probably need some more refinement once things
> progress), and the Windows XenPCI driver enumerates devices as they are
> added to xenstore.
>
> This leaves me with a few questions...
>
> 1. I assume that the qemu virtual BIOS uses the virtual ATA for
> communications. Once my Windows drivers are loaded at boot time (part of
> the bootstrap process I assume), I need to turn off the emulated ATA
> interface so that windows doesn't detect that (two access methods to the
> same block device can't be a good idea!)... how might I get xen/qemu to
> turn that off at a given point... by writing something into xenstore?
>
> 2. I'm presently planning on writing the vbd driver as a Windows SCSI
> miniport driver, which means windows would see the vbd driver as a scsi
> disk. It appears that Xen has a fairly simple idea of single block
> devices, without the concept of buses and controllers. Windows, however,
> likes controller buses with devices hanging off them. So I can create
> one virtual scsi HBA, and just put all the virtual devices on that, or I
> can create one virtual HBA per virtual device... any suggestions? I'm
> not sure that it really matters either way, although the first way seems
> like it would be tidier...
>
> 3. Would the xen list admins consider a new mailing list for a gpl'd
> windows pv driver development? Would you consider providing a place to
> host it under the source control you use (I forget which one :)? Failing
> that I'll just put it up on SourceForge.
>
> Thanks
>
> James
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
>
--
View this message in context: http://www.nabble.com/writing-PV-block-drivers-for-Windows-tf4618069.html#a13305487
Sent from the Xen - Dev mailing list archive at Nabble.com.
next prev parent reply other threads:[~2007-10-20 0:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-13 11:49 writing PV block drivers for Windows James Harper
2007-10-14 1:33 ` Andy Grover
2007-10-14 4:49 ` James Harper
2007-10-14 15:20 ` James Smart
2007-10-14 17:45 ` Alan Cox
2007-10-15 16:58 ` Andy Grover
2007-10-20 0:50 ` Pezza [this message]
2007-10-22 10:49 ` James Harper
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=13305487.post@talk.nabble.com \
--to=mario.beccia@tiscali.it \
--cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.