All of lore.kernel.org
 help / color / mirror / Atom feed
From: benh@kernel.crashing.org (Benjamin Herrenschmidt)
To: linux-arm-kernel@lists.infradead.org
Subject: [kvmarm] [PATCH v3 01/13] KVM: ARM: Introduce KVM_SET_DEVICE_ADDRESS ioctl
Date: Sat, 10 Nov 2012 00:51:19 +1100	[thread overview]
Message-ID: <1352469079.5117.1.camel@pasglop> (raw)
In-Reply-To: <CAFEAcA8FkmNhiemrLaWLGA8=dToHgnwJdrmOknffgLE18sULBg@mail.gmail.com>

On Fri, 2012-11-09 at 14:45 +0100, Peter Maydell wrote:
> On 22 October 2012 08:51, Christoffer Dall
> <c.dall@virtualopensystems.com> wrote:
> > +struct kvm_device_address {
> > +       __u32 id;
> > +       __u64 addr;
> > +};
> 
> Ben suggested that this should either be a 64 bit id or have explicit
> padding. Other than that I think that our current proposed ABI for
> ARM irqchips is in line with the discussion we just had at KVM Forum
> for handling non-x86 in-kernel irqchips [hopefully somebody will
> write the details of that up...]
> 
> Ben, do I have that right?

I believe it is :-)

Cheers,
Ben.

WARNING: multiple messages have this Message-ID (diff)
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Christoffer Dall <c.dall@virtualopensystems.com>,
	kvm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	kvmarm@lists.cs.columbia.edu
Subject: Re: [kvmarm] [PATCH v3 01/13] KVM: ARM: Introduce KVM_SET_DEVICE_ADDRESS ioctl
Date: Sat, 10 Nov 2012 00:51:19 +1100	[thread overview]
Message-ID: <1352469079.5117.1.camel@pasglop> (raw)
In-Reply-To: <CAFEAcA8FkmNhiemrLaWLGA8=dToHgnwJdrmOknffgLE18sULBg@mail.gmail.com>

On Fri, 2012-11-09 at 14:45 +0100, Peter Maydell wrote:
> On 22 October 2012 08:51, Christoffer Dall
> <c.dall@virtualopensystems.com> wrote:
> > +struct kvm_device_address {
> > +       __u32 id;
> > +       __u64 addr;
> > +};
> 
> Ben suggested that this should either be a 64 bit id or have explicit
> padding. Other than that I think that our current proposed ABI for
> ARM irqchips is in line with the discussion we just had at KVM Forum
> for handling non-x86 in-kernel irqchips [hopefully somebody will
> write the details of that up...]
> 
> Ben, do I have that right?

I believe it is :-)

Cheers,
Ben.



  reply	other threads:[~2012-11-09 13:51 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-22  6:51 [PATCH v3 00/13] KVM/ARM vGIC support Christoffer Dall
2012-10-22  6:51 ` Christoffer Dall
2012-10-22  6:51 ` [PATCH v3 01/13] KVM: ARM: Introduce KVM_SET_DEVICE_ADDRESS ioctl Christoffer Dall
2012-10-22  6:51   ` Christoffer Dall
2012-11-09 13:45   ` [kvmarm] " Peter Maydell
2012-11-09 13:45     ` Peter Maydell
2012-11-09 13:51     ` Benjamin Herrenschmidt [this message]
2012-11-09 13:51       ` Benjamin Herrenschmidt
2012-11-10  8:36       ` Christoffer Dall
2012-11-10  8:36         ` Christoffer Dall
2012-10-22  6:51 ` [PATCH v3 02/13] ARM: KVM: Keep track of currently running vcpus Christoffer Dall
2012-10-22  6:51   ` Christoffer Dall
2012-10-22  6:51 ` [PATCH v3 03/13] ARM: KVM: Initial VGIC infrastructure support Christoffer Dall
2012-10-22  6:51   ` Christoffer Dall
2012-10-22  6:51 ` [PATCH v3 04/13] ARM: KVM: Initial VGIC MMIO support code Christoffer Dall
2012-10-22  6:51   ` Christoffer Dall
2012-10-22  6:51 ` [PATCH v3 05/13] ARM: KVM: VGIC accept vcpu and dist base addresses from user space Christoffer Dall
2012-10-22  6:51   ` Christoffer Dall
2012-10-22  6:51 ` [PATCH v3 06/13] ARM: KVM: VGIC distributor handling Christoffer Dall
2012-10-22  6:51   ` Christoffer Dall
2012-10-22  6:52 ` [PATCH v3 07/13] ARM: KVM: VGIC virtual CPU interface management Christoffer Dall
2012-10-22  6:52   ` Christoffer Dall
2012-10-22  6:52 ` [PATCH v3 08/13] ARM: KVM: vgic: retire queued, disabled interrupts Christoffer Dall
2012-10-22  6:52   ` Christoffer Dall
2012-10-22  6:52 ` [PATCH v3 09/13] ARM: KVM: VGIC interrupt injection Christoffer Dall
2012-10-22  6:52   ` Christoffer Dall
2012-10-22  6:52 ` [PATCH v3 10/13] ARM: KVM: VGIC control interface world switch Christoffer Dall
2012-10-22  6:52   ` Christoffer Dall
2012-10-22  6:52 ` [PATCH v3 11/13] ARM: KVM: VGIC initialisation code Christoffer Dall
2012-10-22  6:52   ` Christoffer Dall
2012-10-22  6:52 ` [PATCH v3 12/13] ARM: KVM: vgic: reduce the number of vcpu kick Christoffer Dall
2012-10-22  6:52   ` Christoffer Dall
2012-10-22  6:52 ` [PATCH v3 13/13] ARM: KVM: Add VGIC configuration option Christoffer Dall
2012-10-22  6:52   ` Christoffer Dall

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=1352469079.5117.1.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.