All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: pbonzini@redhat.com, Kevin Wolf <mail@kevin-wolf.de>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/3] multiboot: Fix memory information
Date: Mon, 24 Jun 2013 07:21:10 -0500	[thread overview]
Message-ID: <874ncnd7ih.fsf@codemonkey.ws> (raw)
In-Reply-To: <20130624080242.GA3338@dhcp-200-207.str.redhat.com>

Kevin Wolf <kwolf@redhat.com> writes:

> Am 23.06.2013 um 23:39 hat Anthony Liguori geschrieben:
>> Kevin Wolf <mail@kevin-wolf.de> writes:
>> 
>> > Kevin Wolf (3):
>> >   multiboot: Don't forget last mmap entry
>> >   multiboot: Calculate upper_mem in the ROM
>> >   multiboot: Updated ROM binary
>> 
>> Reviewed-by: Anthony Liguori <aliguori@us.ibm.com>
>> 
>> Do you have a test case that triggered this that you can share?
>
> I haven't seen an actual kernel failure myself, this was reported by
> someone else. But it's easy enough to check with a simple Multiboot
> kernel that just outputs lower_mem/upper_mem and the mmap.
>
> For debugging and fixing I added some throw-away debug code to an
> existing kernel and compared the fixed version with the output when
> loaded by GRUB and it matches now.
>
> If we can have a real test case for this somewhere, I can write a small
> kernel to do the check. Not sure where it would fit though - probably
> kvm-unittests is the closest, even though the test wouldn't really have
> anything to do with KVM.

We could put it in pc-bios even with just a README for now.  Would be
nice to figure out ways to test -kernel as we do find issues often
enough.

It's up to you.  If you had something handy, I was going to add it to my
local test setup.

Regards,

Anthony Liguori

>
>> I'll apply this after a day or so when others have had a chance to review.
>
> Sounds good, thanks.
>
> Kevin

  reply	other threads:[~2013-06-24 12:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-23 20:07 [Qemu-devel] [PATCH 0/3] multiboot: Fix memory information Kevin Wolf
2013-06-23 20:07 ` [Qemu-devel] [PATCH 1/3] multiboot: Don't forget last mmap entry Kevin Wolf
2013-06-23 20:07 ` [Qemu-devel] [PATCH 2/3] multiboot: Calculate upper_mem in the ROM Kevin Wolf
2013-06-23 20:07 ` [Qemu-devel] [PATCH 3/3] multiboot: Updated ROM binary Kevin Wolf
2013-06-23 21:39 ` [Qemu-devel] [PATCH 0/3] multiboot: Fix memory information Anthony Liguori
2013-06-24  8:02   ` Kevin Wolf
2013-06-24 12:21     ` Anthony Liguori [this message]
2013-07-01 13:14 ` Anthony Liguori

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=874ncnd7ih.fsf@codemonkey.ws \
    --to=aliguori@us.ibm.com \
    --cc=kwolf@redhat.com \
    --cc=mail@kevin-wolf.de \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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.