linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] KVM: arm/arm64: Add VGICv3 save/restore API documentation
Date: Fri, 09 Oct 2015 09:06:42 +0100	[thread overview]
Message-ID: <56177592.2080702@arm.com> (raw)
In-Reply-To: <00e601d10264$61cdafb0$25690f10$@samsung.com>

On 09/10/15 08:30, Pavel Fedin wrote:
>  Hello!
> 
>> +  KVM_DEV_ARM_VGIC_CPU_SYSREGS
>> +  Attributes:
>> +    The attr field of kvm_device_attr encodes two values:
>> +    bits:     | 63      ....       32 | 31  ....  16 | 15  ....  0 |
>> +    values:   |         mpidr         |      RES     |    instr    |
> 
>  One small clarification: do you really want it to be different from KVM_DEV_ARM_VGIC_GRP_CPU_REGS?

One is memory mapped, the other one is a system register. One is
addressed by a linear index, the other one by affinity.

How do you reconcile the two? What's the point of trying to shoehorn a
different concept into the existing API?

	M.
-- 
Jazz is not dead. It just smells funny...

  reply	other threads:[~2015-10-09  8:06 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-07 19:50 [PATCH] KVM: arm/arm64: Add VGICv3 save/restore API documentation Christoffer Dall
2015-10-08  7:17 ` Pavel Fedin
2015-10-08  8:23   ` Christoffer Dall
2015-10-08  9:10     ` Pavel Fedin
2015-10-08  9:28       ` Christoffer Dall
2015-10-08 10:14         ` Marc Zyngier
2015-10-08 12:28           ` Pavel Fedin
2015-10-08 12:36             ` Christoffer Dall
2015-10-08 12:45               ` Pavel Fedin
2015-10-08 12:51                 ` Marc Zyngier
2015-10-08 12:55                 ` Peter Maydell
2015-10-08 10:25       ` Peter Maydell
2015-10-09  7:30 ` Pavel Fedin
2015-10-09  8:06   ` Marc Zyngier [this message]
2015-10-09  8:10     ` Pavel Fedin
2015-10-09  8:29       ` Marc Zyngier

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=56177592.2080702@arm.com \
    --to=marc.zyngier@arm.com \
    --cc=linux-arm-kernel@lists.infradead.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).