qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: Sebastian Herbszt <herbszt@gmx.de>
Cc: bochs-developers@lists.sourceforge.net, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [Bochs-developers] [PATCH 5/6] Don't use unreserved memory inBIOS.
Date: Mon, 3 Nov 2008 08:29:56 +0200	[thread overview]
Message-ID: <20081103062956.GF16809@redhat.com> (raw)
In-Reply-To: <415897ECFCCD4BBFADA9C20FB62CD1C4@FSCPC>

On Mon, Nov 03, 2008 at 12:44:26AM +0100, Sebastian Herbszt wrote:
> Gleb Natapov wrote:
>> On Fri, Oct 31, 2008 at 12:12:00AM +0100, Sebastian Herbszt wrote:
>>> Gleb Natapov wrote:
>>>> diff --git a/bios/rombios.h b/bios/rombios.h
>>>> index f0ed88e..57b0f46 100644
>>>> --- a/bios/rombios.h
>>>> +++ b/bios/rombios.h
>>>> @@ -56,7 +56,7 @@
>>>> #define ACPI_DATA_SIZE    0x00010000L
>>>> #define PM_IO_BASE        0xb000
>>>> #define SMB_IO_BASE       0xb100
>>>> -#define CPU_COUNT_ADDR    0xf000
>>>> +#define CPU_COUNT_ADDR    0x0500
>>>
>>> Why did you pick 0x500?
>>>
>> Cool number, don't you think so? It is unused location in a first page.
>> if 0x666 is unused we can use it instead.
>
> Actually 0050h:0000h seems to be used for PRINT-SCREEN STATUS.
> This byte is used by the int 5h service, which is currently not
> implemented. The EBDA could be used here or some reserved BDA
> space (e.g. 0x4d0, 0x4ac).
>
The memory location can be reused after smp initialization.

--
			Gleb.

  reply	other threads:[~2008-11-03  6:30 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-27 10:12 [Qemu-devel] [PATCH 0/6] Support for S3 ACPI state (suspend to memory) in BIOS Gleb Natapov
2008-10-27 10:12 ` [Qemu-devel] [PATCH 1/6] Move PIC initialization out of line to save space in post code area Gleb Natapov
2008-10-27 10:13 ` [Qemu-devel] [PATCH 2/6] Add S3 state to DSDT. Handle resume event in the BIOS Gleb Natapov
2008-10-30 22:41   ` [Qemu-devel] Re: [Bochs-developers] [PATCH 2/6] Add S3 state to DSDT. Handle resumeevent " Sebastian Herbszt
2008-11-02 10:04     ` Gleb Natapov
2008-11-02 18:13       ` [Qemu-devel] Re: [Bochs-developers] [PATCH 2/6] Add S3 state to DSDT. Handleresumeevent " Sebastian Herbszt
2008-11-02 18:39         ` Gleb Natapov
2008-11-02 16:31     ` [Qemu-devel] Re: [Bochs-developers] [PATCH 2/6] Add S3 state to DSDT. Handle resumeevent " Kevin O'Connor
2008-11-02 23:28       ` [Qemu-devel] Re: [Bochs-developers] [PATCH 2/6] Add S3 state to DSDT. Handleresumeevent " Sebastian Herbszt
2008-11-03  0:03         ` Kevin O'Connor
2008-10-27 10:13 ` [Qemu-devel] [PATCH 3/6] Disable init of SMM Gleb Natapov
2008-10-27 10:13 ` [Qemu-devel] [PATCH 4/6] Execute rombios32 code from rom address 0xe0000 Gleb Natapov
2008-10-27 10:13 ` [Qemu-devel] [PATCH 5/6] Don't use unreserved memory in BIOS Gleb Natapov
2008-10-30 23:12   ` [Qemu-devel] Re: [Bochs-developers] " Sebastian Herbszt
2008-11-02 10:06     ` Gleb Natapov
2008-11-02 23:44       ` [Qemu-devel] Re: [Bochs-developers] [PATCH 5/6] Don't use unreserved memory inBIOS Sebastian Herbszt
2008-11-03  6:29         ` Gleb Natapov [this message]
2008-10-27 10:13 ` [Qemu-devel] [PATCH 6/6] Don't power down vga card on entering S3 state 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=20081103062956.GF16809@redhat.com \
    --to=gleb@redhat.com \
    --cc=bochs-developers@lists.sourceforge.net \
    --cc=herbszt@gmx.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).