From: Peter Maydell <peter.maydell@linaro.org>
To: Christoffer Dall <christoffer.dall@linaro.org>
Cc: Patch Tracking <patches@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>,
"kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>
Subject: Re: [Qemu-devel] [RFC PATCH v2 4/4] arm: vgic device control api support
Date: Mon, 14 Oct 2013 14:49:28 +0100 [thread overview]
Message-ID: <CAFEAcA8+R2n71TrW8pDr9WBTn0cbqGRsYORySdbLSS5daAkr7Q@mail.gmail.com> (raw)
In-Reply-To: <1380225373-22132-5-git-send-email-christoffer.dall@linaro.org>
On 26 September 2013 20:56, Christoffer Dall
<christoffer.dall@linaro.org> wrote:
> Support creating the ARM vgic device through the device control API and
> setting the base address for the distributor and cpu interfaces in KVM
> VMs using this API.
>
> Because the older KVM_CREATE_IRQCHIP interface needs the irq chip to be
> created prior to creating the VCPUs, we first test if we can use the
> device control API in kvm_arch_irqchip_create (using the test flag from
> the device control API). If we cannot, it means we have to fall back to
> KVM_CREATE_IRQCHIP and use the older ioctl at this point in time. If
> however, we can use the device control API, we don't do anything and
> wait until the arm_gic_kvm driver initializes and let that use the
> device control API.
>
> Signed-off-by: Christoffer Dall <christoffer.dall@linaro.org>
> + if (ret < 0) {
> + fprintf(stderr, "Failed to set device address: %s\n",
> + strerror(-ret));
> + abort();
> + }
Your indentation here is wrong.
> diff --git a/target-arm/kvm_arm.h b/target-arm/kvm_arm.h
> index 5d14887..ea1805a 100644
> --- a/target-arm/kvm_arm.h
> +++ b/target-arm/kvm_arm.h
> @@ -18,16 +18,22 @@
> * kvm_arm_register_device:
> * @mr: memory region for this device
> * @devid: the KVM device ID
> + * @type: device control API device type
> + * @group: device control API group for setting addresses
> + * @attr: device control API address type
> + * @dev_fd: device control device file descriptor (or -1 if not supported)
This adds documentation for four new parameters...
> -void kvm_arm_register_device(MemoryRegion *mr, uint64_t devid);
> +void kvm_arm_register_device(MemoryRegion *mr, uint64_t devid, uint64_t group,
> + uint64_t attr, int dev_fd);
...but the prototype only adds three (no new 'type'
param).
Looks good otherwise.
-- PMM
prev parent reply other threads:[~2013-10-14 13:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-26 19:56 [Qemu-devel] [RFC PATCH v2 0/4] Create ARM KVM VGIC with device control API Christoffer Dall
2013-09-26 19:56 ` [Qemu-devel] [RFC PATCH v2 1/4] kvm: Update headers for device control api Christoffer Dall
2013-09-26 19:56 ` [Qemu-devel] [RFC PATCH v2 2/4] kvm: Introduce kvm_arch_irqchip_create Christoffer Dall
2013-10-14 13:34 ` Peter Maydell
2013-09-26 19:56 ` [Qemu-devel] [RFC PATCH v2 3/4] kvm: Common device control API functions Christoffer Dall
2013-10-14 13:36 ` Peter Maydell
2013-09-26 19:56 ` [Qemu-devel] [RFC PATCH v2 4/4] arm: vgic device control api support Christoffer Dall
2013-10-14 13:49 ` Peter Maydell [this message]
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=CAFEAcA8+R2n71TrW8pDr9WBTn0cbqGRsYORySdbLSS5daAkr7Q@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=christoffer.dall@linaro.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=patches@linaro.org \
--cc=qemu-devel@nongnu.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).