qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [RFC] Memory API


From: Avi Kivity
Subject: Re: [Qemu-devel] [RFC] Memory API
Date: Thu, 19 May 2011 11:44:59 +0300
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110428 Fedora/3.1.10-1.fc14 Lightning/1.0b3pre Thunderbird/3.1.10

On 05/19/2011 11:30 AM, Jan Kiszka wrote:
>>
>>  That's not that simple. We need to tell apart:
>>   - if a cpu issued the request, and which one =>  forward to APIC
>  And cpu mode may affect where access is forwarded to. If cpu is in SMM
>  mode access to frame buffer may be forwarded to a memory (depends on
>  chipset configuration).

So we have a second use case for CPU-local I/O regions?

I wonder if only a single CPU can enter SMM or if all have to. Right now
only the first CPU can switch to that mode, and that affects the
behaviour of the chipset /wrt SMRAM mapping. Is that another hack?

It's a hack. SMM is a per-cpu setting. Effectively it's another address pin - it changes the meaning of (potentially) all addresses.

--
error compiling committee.c: too many arguments to function




reply via email to

[Prev in Thread] Current Thread [Next in Thread]