| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
RE: [Xen-devel] Driver Architecture Changes
Hmmm... It appears that this has completely broken the
block drivers for ia64. Since it is such a massive change,
I'd imagine it will be difficult to track down the problem(s).
I had rather hoped that we were done with this kind of
massive change pre-3.0.
With Xen/ia64 block devices working in the main tree, I was
going to ask if it might make sense for some basic Xen/ia64
tests to be part of the pre-commit regression test, but alas
I guess I am too late.
Ewan, would you be willing to work with Kevin to get your
re-architected driver infrastructure working on Xen/ia64?
Hopefully it will be easier than I fear but utilizing your direct
expertise with the new architecture, it will be much easier
than Kevin figuring it out from scratch.
Until this is all working again, it won't make much sense to
merge xen-ia64-unstable into xen-unstable, and there are
some fairly critical bug fixes already waiting.
Thanks,
Dan
> From: Ewan Mellor <ewan@xxxxxxxxxxxxx>
> Subject: [Xen-devel] Driver Architecture Changes
> To: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
> Message-ID: <20051115001511.GA28109@xxxxxxxxxxxxxxxxxxxxxx>
> Content-Type: text/plain; charset=us-ascii
>
> I have committed a moderately large change to the device
> driver infrastructure
> in Xen. This change takes large pieces of code from Rusty
> Russell's skeleton
> driver, but with this work refactored so that it is available to all
> Xenbus-based split drivers. This change and it's relation to
> Rusty's work is
> discussed in an email that will follow on immediately.
>
> My intention is that we solidify the driver layer around this
> architecture as
> we head for a Xen 3.0 release. A number of subtle bugs have
> been addressed by
> this change, and the code is now shorter and simpler, which
> should make it
> easier for new drivers to be written too.
>
> I have ported the net and block drivers to this, but not
> blktap, tpmfront, or
> tpmback. I shall be making a first pass over those three drivers very
> shortly, but I would appreciate it if those people who are
> interested in those
> drivers could help with testing and tweaking, as obviously I
> don't understand
> them quite as well as the major drivers.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home