On Fri, 2008-02-22 at 07:25 +, Ian Campbell wrote:
> On Thu, 2008-02-21 at 14:58 -0800, H. Peter Anvin wrote:
> >
> > Which it is on real hardware, because although it's not *reserved*
> > (type 2), it is certainly not made available as *normal memory* (type
> > 1). If Xen maps this as type 1
Add module aliases to support autoprobing modules
for xen frontend devices.
Signed-off-by: Mark McLoughlin <[EMAIL PROTECTED]>
---
drivers/block/xen-blkfront.c |1 +
drivers/net/xen-netfront.c|1 +
drivers/xen/xenbus/xenbus_probe.c | 27 +--
3
Before getting merged, xen-blkfront was xenblk and
xen-netfront was xennet.
Temporarily adding compatibility module aliases
eases upgrades from older versions by e.g. allowing
mkinitrd to find the new version of the module.
Signed-off-by: Mark McLoughlin <[EMAIL PROTECTED]>
---
drivers
On Thu, 2008-02-14 at 17:01 +, Ian Campbell wrote:
> On Thu, 2008-02-14 at 11:34 +0000, Mark McLoughlin wrote:
> > On Wed, 2008-02-13 at 20:54 +, Ian Campbell wrote:
> > > This allows other boot loaders such as the Xen domain builder the
> > > opportun
On Wed, 2008-02-13 at 20:54 +, Ian Campbell wrote:
> This allows other boot loaders such as the Xen domain builder the
> opportunity to extract the ELF file.
Right, Xen currently can't boot bzImage (it needs the ELF image) so you
still can't use the same kernel image on Xen as bare-met
Hi,
after quite a bit of pain in the past figuring out how this all
works and some questions on the kernelnewbies list recently I decided
to do my best to document it.
http://www.skynet.ie/~mark/home/kernel/symbols.html
any comments are welcome..
Cheers,
Mark
-
To unsubscribe from
6 matches
Mail list logo
