From: Sasha Levin <sasha.levin@oracle.com>
To: Marc Zyngier <marc.zyngier@arm.com>
Cc: kvm@vger.kernel.org, kvmarm@lists.cs.columbia.edu,
Sasha Levin <sasha.levin@oracle.com>,
Will Deacon <will.deacon@arm.com>
Subject: Re: [PATCH] kvm tools: add status notification hook to virtio-mmio
Date: Sun, 26 May 2013 11:33:42 -0400 [thread overview]
Message-ID: <51A22B56.6040504@oracle.com> (raw)
In-Reply-To: <1369139376-11921-1-git-send-email-marc.zyngier@arm.com>
On 05/21/2013 08:29 AM, Marc Zyngier wrote:
> Patch e03b449cbddf (kvm tools: add status notification hook for
> virtio) converted virtio-net to use a new notification mechanism,
> but unfortunately left virtio-mmio behind.
>
> The direct consequence is that both arm and arm64 guests are left
> without any form of networking. Not good.
>
> Bring virtio-mmio into this brave new notified world, and feel the
> power of being able to ping again.
>
> Cc: Sasha Levin <sasha.levin@oracle.com>
> Cc: Will Deacon <will.deacon@arm.com>
> Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
> ---
> tools/kvm/virtio/mmio.c | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/tools/kvm/virtio/mmio.c b/tools/kvm/virtio/mmio.c
> index a4e4855..afa2692 100644
> --- a/tools/kvm/virtio/mmio.c
> +++ b/tools/kvm/virtio/mmio.c
> @@ -144,16 +144,21 @@ static void virtio_mmio_config_out(u64 addr, void *data, u32 len,
> struct virtio_device *vdev)
> {
> struct virtio_mmio *vmmio = vdev->virtio;
> + struct kvm *kvm = vmmio->kvm;
> u32 val = 0;
>
> switch (addr) {
> case VIRTIO_MMIO_HOST_FEATURES_SEL:
> case VIRTIO_MMIO_GUEST_FEATURES_SEL:
> case VIRTIO_MMIO_QUEUE_SEL:
> - case VIRTIO_MMIO_STATUS:
> val = ioport__read32(data);
> *(u32 *)(((void *)&vmmio->hdr) + addr) = val;
> break;
> + case VIRTIO_MMIO_STATUS:
> + vmmio->hdr.status = ioport__read32(data);
> + if (vdev->ops->notify_status)
> + vdev->ops->notify_status(kvm, vmmio->dev, vmmio->hdr.status);
> + break;
> case VIRTIO_MMIO_GUEST_FEATURES:
> if (vmmio->hdr.guest_features_sel == 0) {
> val = ioport__read32(data);
>
Pekka, could you apply please?
Acked-by: Sasha Levin <sasha.levin@oracle.com>
Thanks,
Sasha
next prev parent reply other threads:[~2013-05-26 15:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-21 12:29 [PATCH] kvm tools: add status notification hook to virtio-mmio Marc Zyngier
2013-05-26 15:33 ` Sasha Levin [this message]
2013-05-27 0:10 ` Asias He
2013-06-10 14:22 ` Will Deacon
2013-06-10 14:39 ` Pekka Enberg
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=51A22B56.6040504@oracle.com \
--to=sasha.levin@oracle.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=marc.zyngier@arm.com \
--cc=will.deacon@arm.com \
/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.