All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Limpach <christian.limpach@gmail.com>
To: Michal Ostrowski <mostrows@watson.ibm.com>
Cc: xen-devel@lists.sourceforge.net, kaf24@cl.cam.ac.uk, iap10@cl.cam.ac.uk
Subject: Re: RFC/Patch: Support for other bootloaders
Date: Wed, 23 Mar 2005 20:40:58 +0000	[thread overview]
Message-ID: <3d8eece205032312404294db9d@mail.gmail.com> (raw)
In-Reply-To: <1111419962.4293.128.camel@brick.watson.ibm.com>

On Mon, 21 Mar 2005 10:46:02 -0500, Michal Ostrowski
<mostrows@watson.ibm.com> wrote:
> 
> I need to net-boot xen on an HS20 blade.  HS20's have a Broadcom NIC,
> which is not supported by grub.  The attached patch allows me to build a
> Xen image which I can boot using PXELinux  (and the entire SysLinux
> family of boot-loaders).

I think this breaks multiboot support because of:
+void __init __start_xen(void *params)
+{
...
+    multiboot_info_t *mbi = NULL;
+    
+    if (MULTIBOOT_BOOTLOADER_MAGIC == *(u32*)params ) 
+    {
+        mbi = (struct multiboot_info_t*)__va(mbi);

I think this should be:
+    if (MULTIBOOT_BOOTLOADER_MAGIC == *(u32*)__va(params) ) 
+    {
+        mbi = (struct multiboot_info_t*)__va(params);

Also, have you tested your changes on a SMP or HT machine?  I think
you're lucky if it works at all because you rearranged some of the
tests, and now the test for multiboot is no longer protected by the
test if we're running on a secondary cpu (%ebx == 0).

Finally, I think the updated mbootpack is a sufficient solution --
we're trying to fix a limitation in most bootloaders and interposing
something which works around this limitation seems like a sane
approach...

    christian


-------------------------------------------------------
This SF.net email is sponsored by Microsoft Mobile & Embedded DevCon 2005
Attend MEDC 2005 May 9-12 in Vegas. Learn more about the latest Windows
Embedded(r) & Windows Mobile(tm) platforms, applications & content.  Register
by 3/29 & save $300 http://ads.osdn.com/?ad_id=6883&alloc_id=15149&op=click

  parent reply	other threads:[~2005-03-23 20:40 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-21 15:46 RFC/Patch: Support for other bootloaders Michal Ostrowski
2005-03-21 16:26 ` Tim Deegan
2005-03-21 21:04   ` Michal Ostrowski
2005-03-23 20:40 ` Christian Limpach [this message]
2005-03-23 23:15   ` Michal Ostrowski
  -- strict thread matches above, loose matches on Subject: below --
2005-03-23 17:30 Ian Pratt
2005-03-24 14:27 ` Michal Ostrowski
2005-03-23 15:52 Ian Pratt
2005-03-23 16:10 ` Michal Ostrowski
2005-03-23 16:23 ` Tim Deegan
2005-03-23 16:44   ` Michal Ostrowski
2005-03-23 16:57   ` Anthony Liguori
2005-03-23 16:56 ` Jeremy Katz
2005-03-23 23:39   ` Michal Ostrowski
2005-03-22  9:29 Ian Pratt
2005-03-22 14:18 ` Michal Ostrowski
2005-03-22 14:42   ` Tim Deegan
2005-03-22 15:05     ` Michal Ostrowski
2005-03-23 11:20     ` Tim Deegan
2005-03-23 13:00       ` Michal Ostrowski
2005-03-23 16:09       ` Anthony Liguori
2005-03-21 21:57 Ian Pratt
2005-03-21 23:01 ` Tim Deegan
2005-03-21 23:35   ` Michal Ostrowski
2005-03-22  9:17     ` Keir Fraser
2005-03-22  0:08   ` Michal Ostrowski
2005-03-21 12:15 Michal Ostrowski

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=3d8eece205032312404294db9d@mail.gmail.com \
    --to=christian.limpach@gmail.com \
    --cc=Christian.Limpach@cl.cam.ac.uk \
    --cc=iap10@cl.cam.ac.uk \
    --cc=kaf24@cl.cam.ac.uk \
    --cc=mostrows@watson.ibm.com \
    --cc=xen-devel@lists.sourceforge.net \
    /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.