From: Will Deacon <will.deacon@arm.com>
To: Andre Przywara <andre.przywara@arm.com>
Cc: "kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
Marc Zyngier <Marc.Zyngier@arm.com>
Subject: Re: [PATCH 2/4] kvmtool: prepare for instantiating different IRQ chip devices
Date: Fri, 20 Jun 2014 18:55:19 +0100 [thread overview]
Message-ID: <20140620175519.GF30656@arm.com> (raw)
In-Reply-To: <1403181879-29908-3-git-send-email-andre.przywara@arm.com>
Hi Andre,
On Thu, Jun 19, 2014 at 01:44:37PM +0100, Andre Przywara wrote:
> Extend the vGIC handling code to deal with different IRQ chip devices
> instead of hard-coding the GICv2 in.
Minor comment, but there are a few stray pr_infos in here which I don't
think are especially useful.
> + if (!ioctl(gic_fd, KVM_HAS_DEVICE_ATTR, &offset_attr)) {
> + err = ioctl(gic_fd, KVM_GET_DEVICE_ATTR, &offset_attr);
> + if (err)
> + return err;
> + }
> +
> + cpu_if_addr += offset;
> +
> + err = ioctl(gic_fd, KVM_SET_DEVICE_ATTR, &cpu_if_attr);
> if (err)
> return err;
> + pr_info("creating GICv2 KVM device");
One here...
> + switch (type) {
> + case KVM_DEV_TYPE_ARM_VGIC_V2:
> + compatible = "arm,cortex-a15-gic";
> + pr_info("creating FDT for a GICv2");
... and here.
> diff --git a/tools/kvm/virtio/mmio.c b/tools/kvm/virtio/mmio.c
> index afae6a7..35dc113 100644
> --- a/tools/kvm/virtio/mmio.c
> +++ b/tools/kvm/virtio/mmio.c
> @@ -293,7 +293,7 @@ int virtio_mmio_init(struct kvm *kvm, void *dev, struct virtio_device *vdev,
> *
> * virtio_mmio.devices=0x200@0xd2000000:5,0x200@0xd2000200:6
> */
> - pr_info("virtio-mmio.devices=0x%x@0x%x:%d\n", VIRTIO_MMIO_IO_SIZE, vmmio->addr, line);
> + pr_info("virtio-mmio.devices=0x%x@0x%x:%d", VIRTIO_MMIO_IO_SIZE, vmmio->addr, line);
Huh?
Anyway, the general idea looks ok to me.
Will
next prev parent reply other threads:[~2014-06-20 17:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-19 12:44 [PATCH 0/4] kvmtool: Add GICv3 emulation support Andre Przywara
2014-06-19 12:44 ` [PATCH 1/4] kvmtool: public header definitions from GICv3 emulation patch series Andre Przywara
2014-06-19 12:44 ` [PATCH 2/4] kvmtool: prepare for instantiating different IRQ chip devices Andre Przywara
2014-06-20 17:55 ` Will Deacon [this message]
2014-06-19 12:44 ` [PATCH 3/4] kvmtool: add support for supplying GICv3 redistributor addresses Andre Przywara
2014-06-19 12:44 ` [PATCH 4/4] kvmtool: add command line parameter to instantiate a vGICv3 Andre Przywara
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=20140620175519.GF30656@arm.com \
--to=will.deacon@arm.com \
--cc=Marc.Zyngier@arm.com \
--cc=andre.przywara@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
/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.