All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Graf <agraf@suse.de>
To: Avi Kivity <avi@redhat.com>
Cc: kwolf@redhat.com, rene@exactcode.de, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 3/4] Multiboot support v2
Date: Thu, 18 Jun 2009 12:22:20 +0200	[thread overview]
Message-ID: <662EA648-D416-4632-9095-DF622950E955@suse.de> (raw)
In-Reply-To: <4A3A0F5F.8090007@redhat.com>


On 18.06.2009, at 11:56, Avi Kivity wrote:

> On 06/17/2009 07:41 PM, Alexander Graf wrote:
>> This patch implements support for Multiboot on x86 for -kernel.
>> Multiboot is a "new" approach to get rid of different bootloaders,  
>> providing
>> a unified interface for the kernel. It supports command line  
>> options and
>> kernel modules.
>>
>> The two probably best known projects using multiboot are Xen and  
>> GNU Hurd.
>>
>> This implementation should be mostly feature-complete. It is  
>> missing VBE
>> extensions, but as no system uses them currently it does not really  
>> hurt.
>>
>> To use multiboot, specify the kernel as -kernel option. Modules  
>> should be given
>> as -initrd options, seperated by a comma (,). -append also works.
>>
>> Please bear in mind that grub also does gzip decompression, which  
>> qemu does
>> not do yet. To run existing images, please ungzip them first.
>>
>> The guest multiboot loader code is implemented as option rom using  
>> int 19.
>> Parts of the work are based on efforts by Rene Rebe, who originally  
>> ported
>> my code to int 19.
>>
>
> This will be very useful for running test cases.
>
>> +    /* Ok, let's see if it is a multiboot image.
>> +       The header is 12x32bit long, so the latest entry may be  
>> 8192 - 48. */
>> +    for(i = 0; i<  (8192 - 48); i += 4) {
>>
>
> Here (and in many other places in the patch) you have a control flow  
> keyword followed immediately by a parentheses, so it looks like a  
> function call.  Really reduced readability IMO.

Looking through pc.c I found for mostly without space, but if with  
immediate space after it.

Wouldn't it be more useful to write some automatic formatting script  
git would run on patches that go in? Maybe people using tabs in the  
wrong areas of the code would be able to submit patches by then too ;-).

IMHO there is no real "qemu coding style" atm anyway - each maintainer  
has his own and uses that for its subtree. It'd be a lot more helpful  
to start addressing things at the root of the problems.

Alex

  reply	other threads:[~2009-06-18 10:22 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-17 16:41 [Qemu-devel] [PATCH 0/4] Add multiboot support (x86) v2 Alexander Graf
2009-06-17 16:41 ` [Qemu-devel] [PATCH 1/4] Change bochs bios init order Alexander Graf
2009-06-17 16:41   ` [Qemu-devel] [PATCH 2/4] Expose fw_cfg v2 Alexander Graf
2009-06-17 16:41     ` [Qemu-devel] [PATCH 3/4] Multiboot support v2 Alexander Graf
2009-06-17 16:41       ` [Qemu-devel] [PATCH 4/4] Multiboot build system Alexander Graf
2009-06-18  9:56       ` [Qemu-devel] [PATCH 3/4] Multiboot support v2 Avi Kivity
2009-06-18 10:22         ` Alexander Graf [this message]
2009-06-18 11:19           ` Avi Kivity
2009-06-17 17:10 ` [Qemu-devel] [PATCH 0/4] Add multiboot support (x86) v2 François Revol
2009-06-17 17:59   ` Anthony Liguori
2009-06-18  8:25     ` François Revol
2009-06-18  9:09       ` Kevin Wolf
2009-06-18 11:44         ` François Revol
2009-06-18 11:55           ` Alexander Graf
2009-06-18 12:13             ` François Revol
2009-06-18 12:01           ` Kevin Wolf
2009-06-18 12:17             ` François Revol
2009-06-18 12:23               ` Alexander Graf
2009-06-18 12:34                 ` François Revol
2009-06-18 12:29               ` Kevin Wolf
2009-06-18 12:35                 ` François Revol
2009-06-18 11:15 ` Gleb Natapov

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=662EA648-D416-4632-9095-DF622950E955@suse.de \
    --to=agraf@suse.de \
    --cc=avi@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rene@exactcode.de \
    /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.