[Android-virt] [PATCH 6/8] ARM: KVM: table-driven coprocessor emulation.

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

 



On 14 March 2012 00:49, Rusty Russell <rusty at rustcorp.com.au> wrote:
> On Tue, 13 Mar 2012 08:47:52 +0000, Peter Maydell <peter.maydell at linaro.org> wrote:
>> Are you going to want to encode "this is how this cp15 register
>> is reset" in your tables at some point? Or "r/o for user mode
>> but r/w for kernel" or other complicated permissions?
>
> I think reset values deserve a separate table, since it's not an obvious
> fit here.

Hmm. Isn't that going to make it hard to say "this register is
present on both CPU Foo and CPU Bar", since the details of what
'this register' means will be spread across an MRC line, an MCR
line and an entry in a separate reset value table?

(I don't have any great design ideas here, I'm still struggling
with the equivalent problem in QEMU...)

-- PMM


[Index of Archives]     [Linux KVM]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux