Re: handling cp15 state which isn't trivially exposed as a single register

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

 



On 21.08.2012, at 00:28, Peter Maydell wrote:

> On 20 August 2012 23:18, Alexander Graf <agraf@xxxxxxx> wrote:
>> My question still holds. Why not use ONE_REG for this? What advantage
>> does GET/SET_MSRS give you?
> 
> It lets you set more than one register at once, and it follows
> the pattern x86 already has (with a GET, SET, and a LIST_INDEX
> for finding out what the kernel actually supports).

Maybe we should sit down and generalize those features and make them available to everyone rather than shoehorning ARM into an x86 only ioctl then?


Alex


_______________________________________________
kvmarm mailing list
kvmarm@xxxxxxxxxxxxxxxxxxxxx
https://lists.cs.columbia.edu/cucslists/listinfo/kvmarm


[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