From: "Daniel P. Berrange" <berrange@redhat.com>
To: Pat Campbell <plc@novell.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: RFC: Xen cdrom haldaemon
Date: Wed, 5 Sep 2007 18:56:33 +0100 [thread overview]
Message-ID: <20070905175633.GI5503@redhat.com> (raw)
In-Reply-To: <46DE8884.3E48.0018.0@novell.com>
On Wed, Sep 05, 2007 at 10:43:30AM -0600, Pat Campbell wrote:
> The basic flow of the patch is:
>
> Kernel:
> blkback driver:
> if block device is a physical cdrom then
> Add media_present=1 into xenstore backend/vbd
> for this device
> Place a xenstore watch on media_present
>
> watch_handler
> if watch token is media_present
> read value
> if 0 then close block device fd
> if 1 then re-open block device fd
>
> Any access with fd closed results in EACCESS error
>
> qemu
> if block device is a cdrom
> Place a xenstore watch on media_present
> watch_handler
> if watch token is media_present
> read value
> if 0 then close block device
> if 1 then re-open block device and set media_changed
>
> Any access with fd closed results in EACCESS error
>
> xend
> Starts XEN HalDaemon process
>
> XEN HalDaemon
> Registers event callback for HALD events
> callback handler
> gets device major/minor numbers
> for each vbd in xenstore
> if matching major and minor
> if add_event ( cdrom door closed with media )
> xenstore write 1 to vbd/media_present
> else ( cddrom door open )
> xenstore write 0 to vbd/media_present
>
> I am just learning python, could use a python guy to enhance and
> generalize.
To be honest this sounds like rather overkill. Why on earth is blkback
opening the device in the first place? blkback/blkfront don't have any
kind of support for CDROM capabilities, so paravirt drivers for a disk
device Xend marked as a cdrom don't make sense. If we stop blkback from
processing any devices with the ':cdrom' annotation, then only QEMU will
have the device open & the problem should go away if I'm understanding
your description properly.
Dan.
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=|
|=- Perl modules: http://search.cpan.org/~danberr/ -=|
|=- Projects: http://freshmeat.net/~danielpb/ -=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
next prev parent reply other threads:[~2007-09-05 17:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-03 14:34 RFC: Xen 3.1.1 Keir Fraser
2007-09-03 19:18 ` Daniel P. Berrange
2007-09-04 7:12 ` Keir Fraser
2007-09-04 13:30 ` Daniel P. Berrange
2007-09-05 16:43 ` RFC: Xen cdrom haldaemon Pat Campbell
2007-09-05 17:39 ` Keir Fraser
2007-09-06 13:13 ` Pat Campbell
2007-09-05 17:56 ` Daniel P. Berrange [this message]
2007-09-06 14:05 ` Pat Campbell
2007-09-03 23:00 ` RFC: Xen 3.1.1 James Harper
2007-09-04 0:32 ` John Levon
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=20070905175633.GI5503@redhat.com \
--to=berrange@redhat.com \
--cc=plc@novell.com \
--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.