qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eduardo Habkost <ehabkost@redhat.com>
To: Peng Hao <peng.hao2@zte.com.cn>
Cc: pbonzini@redhat.com, mst@redhat.com, rkrcmar@redhat.com,
	kvm@vger.kernel.org, qemu-devel@nongnu.org,
	zhong.weidong@zte.com.cn
Subject: Re: [Qemu-devel] [PATCH V4 1/4] target-i386: introduce coalesced_pio kvm header update
Date: Tue, 28 Aug 2018 11:58:15 -0300	[thread overview]
Message-ID: <20180828145815.GJ5675@localhost.localdomain> (raw)
In-Reply-To: <1535199590-68475-2-git-send-email-peng.hao2@zte.com.cn>

On Sat, Aug 25, 2018 at 08:19:47PM +0800, Peng Hao wrote:
> add coalesced_pio's struct and KVM_CAP_COALESCED_PIO header.
> 
> Signed-off-by: Peng Hao <peng.hao2@zte.com.cn>

What's the status of the corresponding KVM header patch?


> ---
>  accel/kvm/kvm-all.c       | 4 ++--
>  linux-headers/linux/kvm.h | 5 +++--
>  2 files changed, 5 insertions(+), 4 deletions(-)
> 
> diff --git a/accel/kvm/kvm-all.c b/accel/kvm/kvm-all.c
> index eb7db92..4a3909d 100644
> --- a/accel/kvm/kvm-all.c
> +++ b/accel/kvm/kvm-all.c
> @@ -536,7 +536,7 @@ static void kvm_coalesce_mmio_region(MemoryListener *listener,
>  
>          zone.addr = start;
>          zone.size = size;
> -        zone.pad = 0;
> +        zone.pio = 0;
>  
>          (void)kvm_vm_ioctl(s, KVM_REGISTER_COALESCED_MMIO, &zone);
>      }
> @@ -553,7 +553,7 @@ static void kvm_uncoalesce_mmio_region(MemoryListener *listener,
>  
>          zone.addr = start;
>          zone.size = size;
> -        zone.pad = 0;
> +        zone.pio = 0;
>  
>          (void)kvm_vm_ioctl(s, KVM_UNREGISTER_COALESCED_MMIO, &zone);
>      }
> diff --git a/linux-headers/linux/kvm.h b/linux-headers/linux/kvm.h
> index 98f389a..747b473 100644
> --- a/linux-headers/linux/kvm.h
> +++ b/linux-headers/linux/kvm.h
> @@ -420,13 +420,13 @@ struct kvm_run {
>  struct kvm_coalesced_mmio_zone {
>  	__u64 addr;
>  	__u32 size;
> -	__u32 pad;
> +	__u32 pio;
>  };
>  
>  struct kvm_coalesced_mmio {
>  	__u64 phys_addr;
>  	__u32 len;
> -	__u32 pad;
> +	__u32 pio;
>  	__u8  data[8];
>  };
>  
> @@ -949,6 +949,7 @@ struct kvm_ppc_resize_hpt {
>  #define KVM_CAP_GET_MSR_FEATURES 153
>  #define KVM_CAP_HYPERV_EVENTFD 154
>  #define KVM_CAP_HYPERV_TLBFLUSH 155
> +#define KVM_CAP_COALESCED_PIO 156
>  
>  #ifdef KVM_CAP_IRQ_ROUTING
>  
> -- 
> 1.8.3.1
> 

-- 
Eduardo

  reply	other threads:[~2018-08-28 15:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-25 12:19 [Qemu-devel] [PATCH V4 0/4] introduce coalesced pio support Peng Hao
2018-08-25 12:19 ` [Qemu-devel] [PATCH V4 1/4] target-i386: introduce coalesced_pio kvm header update Peng Hao
2018-08-28 14:58   ` Eduardo Habkost [this message]
2018-08-29 16:50     ` Radim Krčmář
2018-08-25 12:19 ` [Qemu-devel] [PATCH V4 2/4] target-i386:add coalesced_pio API Peng Hao
2018-08-29 16:43   ` Eduardo Habkost
2018-08-25 12:19 ` [Qemu-devel] [PATCH V4 3/4] target-i386: add rtc 0x70 port as coalesced_pio Peng Hao
2018-08-25 12:19 ` [Qemu-devel] [PATCH V4 4/4] target-i386: add i440fx 0xcf8 " Peng Hao
2018-08-25 23:29   ` Liran Alon
2018-08-28 14:57 ` [Qemu-devel] [PATCH V4 0/4] introduce coalesced pio support Eduardo Habkost

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=20180828145815.GJ5675@localhost.localdomain \
    --to=ehabkost@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peng.hao2@zte.com.cn \
    --cc=qemu-devel@nongnu.org \
    --cc=rkrcmar@redhat.com \
    --cc=zhong.weidong@zte.com.cn \
    /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).