This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] [Patch][2/2][BIOS] Support BCV table

To: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [Patch][2/2][BIOS] Support BCV table
From: Akio Takebe <takebe_akio@xxxxxxxxxxxxxx>
Date: Fri, 27 Mar 2009 23:22:03 +0900
Cc: Akio Takebe <takebe_akio@xxxxxxxxxxxxxx>
Delivery-date: Fri, 27 Mar 2009 07:22:54 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C5F289DE.526B%keir.fraser@xxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <C5F289DE.526B%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
>On 27/03/2009 10:31, "Akio Takebe" <takebe_akio@xxxxxxxxxxxxxx> wrote:
>> I don't try the idea of vendor:dev id, but I made a patch(bcv.v2.patch)
>> adding the feature of retrying to boot with the next drives.
>> What do you think about this patch?
>> This patch doesn't add any new syntax, just add the retry feature.
>> Also I made another patch(support_interactive_boot_for_bcv.patch).
>> It allows user to select a bootable pass-through device with F12.
>> support_interactive_boot_for_bcv.patch depends on bcv.v2.patch.
>Both are plausible. Looking at your previous email, I get the impression
>that the limitations are in rombios, and/or its integration with hvmloader.
>Would the right fix really to make rombios be a bit smarter: being able to
>load and discard option ROMs into 0xc0000-0xe0000 range, for example? Also,
Thanks. Yes, you are right.

>I have the view that parts of rombios's POST routines could get moved into
>hvmloader, even if we keep rombios for its real-mode BIOS service routines,
>after POST. Actually I'd be happy to see hvmloader get a bit fatter at
>rombios's expense! Perhaps this is a possibility for the Xen 3.5 development
OK, I will also improve my patch with your idea of vendor:dev id
for Xen-3.5.

Best Regards,

Akio Takebe

Xen-devel mailing list