From: Anthony Liguori <aliguori@us.ibm.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: Chris Wright <chrisw@sous-sol.org>,
virtualization@lists.osdl.org, xen-devel@lists.xensource.com,
linux-kernel@vger.kernel.org, Ian Pratt <ian.pratt@xensource.com>,
ian.pratt@cl.cam.ac.uk
Subject: Re: [RFC PATCH 35/35] Add Xen virtual block device driver.
Date: Wed, 22 Mar 2006 11:09:13 -0600 [thread overview]
Message-ID: <442184B9.2020507@us.ibm.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D4B9E8A@liverpoolst.ad.cl.cam.ac.uk>
Ian Pratt wrote:
>> This seems to be pretty evil and creating interesting failure
>> conditions for users who load IDE or SCSI modules. I've seen
>> it trip up a number of people in the past. I think we should
>> only ever use the major number that was actually allocated to us.
>>
>
> We certainly should be pushing everyone toward using the 'xdX' etc
> devices that are allocated to us. However, the installers of certain
> older distros and other user space tools won't except anything other
> than hdX/sdX, so its useful from a compatibility POV even if it never
> goes into mainline, which I agree it probably shouldn't.
>
Then perhaps we should deprecate non xd block devices starting in the
near future (3.0.3?). We probably need to have it deprecated for a few
releases since I think most people are not using xd at this point...
Regards,
Anthony Liguori
> Ian
>
WARNING: multiple messages have this Message-ID (diff)
From: Anthony Liguori <aliguori@us.ibm.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com,
Ian Pratt <ian.pratt@xensource.com>,
linux-kernel@vger.kernel.org, Chris Wright <chrisw@sous-sol.org>,
virtualization@lists.osdl.org
Subject: Re: [RFC PATCH 35/35] Add Xen virtual block device driver.
Date: Wed, 22 Mar 2006 11:09:13 -0600 [thread overview]
Message-ID: <442184B9.2020507@us.ibm.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D4B9E8A@liverpoolst.ad.cl.cam.ac.uk>
Ian Pratt wrote:
>> This seems to be pretty evil and creating interesting failure
>> conditions for users who load IDE or SCSI modules. I've seen
>> it trip up a number of people in the past. I think we should
>> only ever use the major number that was actually allocated to us.
>>
>
> We certainly should be pushing everyone toward using the 'xdX' etc
> devices that are allocated to us. However, the installers of certain
> older distros and other user space tools won't except anything other
> than hdX/sdX, so its useful from a compatibility POV even if it never
> goes into mainline, which I agree it probably shouldn't.
>
Then perhaps we should deprecate non xd block devices starting in the
near future (3.0.3?). We probably need to have it deprecated for a few
releases since I think most people are not using xd at this point...
Regards,
Anthony Liguori
> Ian
>
next prev parent reply other threads:[~2006-03-22 17:09 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-22 16:52 [RFC PATCH 35/35] Add Xen virtual block device driver Ian Pratt
2006-03-22 16:52 ` Ian Pratt
2006-03-22 17:09 ` Anthony Liguori [this message]
2006-03-22 17:09 ` Anthony Liguori
2006-03-22 23:09 ` Jeff Garzik
2006-03-24 12:17 ` Alan Cox
2006-03-24 12:38 ` Jeff Garzik
2006-03-24 13:37 ` Jeff Garzik
2006-03-24 13:40 ` Arjan van de Ven
2006-03-24 13:50 ` Jeff Garzik
2006-03-24 15:33 ` Dave C Boutcher
2006-03-24 19:04 ` Mike Christie
2006-03-24 19:04 ` Mike Christie
2006-03-24 19:19 ` Dave C Boutcher
2006-03-25 0:32 ` FUJITA Tomonori
2006-03-25 0:47 ` Roland Dreier
2006-03-25 0:47 ` Roland Dreier
2006-03-24 15:55 ` Alan Cox
2006-03-24 15:55 ` Alan Cox
2006-03-25 10:03 ` Rusty Russell
2006-03-25 10:03 ` Rusty Russell
2006-03-27 10:14 ` Peter Chubb
2006-03-23 8:19 ` Arjan van de Ven
2006-03-23 9:34 ` Keir Fraser
2006-03-23 9:34 ` Keir Fraser
2006-03-23 9:41 ` Arjan van de Ven
2006-03-23 9:42 ` Arjan van de Ven
-- strict thread matches above, loose matches on Subject: below --
2006-05-09 8:49 [RFC PATCH 00/35] Xen i386 paravirtualization support Chris Wright
2006-05-09 7:00 ` [RFC PATCH 35/35] Add Xen virtual block device driver Chris Wright
2006-05-09 12:01 ` Christoph Hellwig
2006-03-22 6:30 [RFC PATCH 00/35] Xen i386 paravirtualization support Chris Wright
2006-03-22 6:31 ` [RFC PATCH 35/35] Add Xen virtual block device driver Chris Wright
2006-03-22 16:39 ` Anthony Liguori
2006-03-22 16:54 ` Christoph Hellwig
2006-03-27 8:42 ` Gerd Hoffmann
2006-03-27 8:42 ` Gerd Hoffmann
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=442184B9.2020507@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=chrisw@sous-sol.org \
--cc=ian.pratt@cl.cam.ac.uk \
--cc=ian.pratt@xensource.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=virtualization@lists.osdl.org \
--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.