qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
To: qemu-devel@nongnu.org
Cc: bochs-developers@lists.sourceforge.net, 'Gleb Natapov' <gleb@redhat.com>
Subject: Re: [Bochs-developers] [Qemu-devel] [PATCH v5 0/5] Support for	S3 ACPI state (suspend	to memory) in BIOS
Date: Thu, 27 Nov 2008 20:07:36 +0100	[thread overview]
Message-ID: <492EEFF8.50802@gmx.net> (raw)
In-Reply-To: <000301c950c2$4e2058b0$ea610a10$@com>

On 27.11.2008 19:59, Stanislav wrote:
> In Bochs CPU doesn't have a cache memory emulated to use it as RAM but it is
> still possible to emulate cache-as-ram mode.
> The problem that cache-as-ram mode is very very very processor specific and
> implementation of it might be different between Intel and AMD for example.
> Which one to pick up ?
>   

I have worked on Intel, AMD and VIA implementations for Cache-as-RAM.
Avi Kivity suggested a simple algorithm which is a catchall for Intel
586, Intel Core 2 Duo, AMD K8, AMD K10 and VIA C7.

> Or might be better to invent some other mode especially for emulation
> reasons ?
>   

With the catchall emulation, inventing a special mode should be unneeded.

Regards,
Carl-Daniel

-- 
http://www.hailfinger.org/

  reply	other threads:[~2008-11-27 19:07 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-27 11:02 [Qemu-devel] [PATCH v5 0/5] Support for S3 ACPI state (suspend to memory) in BIOS Gleb Natapov
2008-11-27 11:02 ` [Qemu-devel] [PATCH v5 1/5] Add S3 state to DSDT. Handle resume event in the BIOS Gleb Natapov
2008-12-07  2:57   ` [Qemu-devel] Re: [Bochs-developers] " Kevin O'Connor
2008-12-07  9:20     ` Gleb Natapov
2008-12-07 15:10       ` Kevin O'Connor
2008-12-07 16:31         ` Gleb Natapov
2008-12-09 22:26       ` [Qemu-devel] Re: [Bochs-developers] [PATCH v5 1/5] Add S3 state to DSDT.Handle " Sebastian Herbszt
2008-12-10  0:06         ` Kevin O'Connor
2008-12-10 10:22           ` Gleb Natapov
2008-12-09 13:38     ` [Qemu-devel] Re: [Bochs-developers] [PATCH v5 1/5] Add S3 state to DSDT. Handle " Gleb Natapov
2008-12-09 15:12       ` [Qemu-devel] " Stanislav
2008-12-14 22:02       ` [Qemu-devel] Re: [Bochs-developers] [PATCH v5 1/5] Add S3 state to DSDT.Handle " Sebastian Herbszt
2008-11-27 11:02 ` [Qemu-devel] [PATCH v5 2/5] Preserve memory content during SMM init Gleb Natapov
2008-11-27 11:02 ` [Qemu-devel] [PATCH v5 3/5] Execute rombios32 code from rom address 0xe0000 Gleb Natapov
2008-11-27 11:02 ` [Qemu-devel] [PATCH v5 4/5] Don't use unreserved memory in BIOS Gleb Natapov
2008-11-27 11:02 ` [Qemu-devel] [PATCH v5 5/5] Don't power down vga card on entering S3 state Gleb Natapov
2008-11-27 12:17 ` [Qemu-devel] [PATCH v5 0/5] Support for S3 ACPI state (suspend to memory) in BIOS Carl-Daniel Hailfinger
2008-11-27 12:35   ` Gleb Natapov
2008-11-27 18:59     ` [Bochs-developers] " Stanislav
2008-11-27 19:07       ` Carl-Daniel Hailfinger [this message]
2008-11-27 20:04         ` Stanislav
2008-11-27 21:04           ` Carl-Daniel Hailfinger
2008-11-29 19:42             ` Stanislav
2008-12-04 10:04               ` Carl-Daniel Hailfinger

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=492EEFF8.50802@gmx.net \
    --to=c-d.hailfinger.devel.2006@gmx.net \
    --cc=bochs-developers@lists.sourceforge.net \
    --cc=gleb@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 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).