From: "Radim Krčmář" <rkrcmar@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: Peng Hao <peng.hao2@zte.com.cn>,
zhong.weidong@zte.com.cn, kvm@vger.kernel.org, mst@redhat.com,
qemu-devel@nongnu.org, pbonzini@redhat.com
Subject: Re: [PATCH V4 1/4] target-i386: introduce coalesced_pio kvm header update
Date: Wed, 29 Aug 2018 18:50:54 +0200 [thread overview]
Message-ID: <20180829165053.GA19438@flask> (raw)
In-Reply-To: <20180828145815.GJ5675@localhost.localdomain>
2018-08-28 11:58-0300, Eduardo Habkost:
> 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?
I got a minor request to improve compatibility and although the series
has missed the kernel merge window, we can reserve the capability number
within a week.
WARNING: multiple messages have this Message-ID (diff)
From: "Radim Krčmář" <rkrcmar@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: Peng Hao <peng.hao2@zte.com.cn>,
pbonzini@redhat.com, mst@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: Wed, 29 Aug 2018 18:50:54 +0200 [thread overview]
Message-ID: <20180829165053.GA19438@flask> (raw)
In-Reply-To: <20180828145815.GJ5675@localhost.localdomain>
2018-08-28 11:58-0300, Eduardo Habkost:
> 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?
I got a minor request to improve compatibility and although the series
has missed the kernel merge window, we can reserve the capability number
within a week.
next prev parent reply other threads:[~2018-08-29 16:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-25 12:19 [PATCH V4 0/4] introduce coalesced pio support Peng Hao
2018-08-25 12:19 ` [Qemu-devel] " Peng Hao
2018-08-25 12:19 ` [PATCH V4 1/4] target-i386: introduce coalesced_pio kvm header update Peng Hao
2018-08-25 12:19 ` [Qemu-devel] " Peng Hao
2018-08-28 14:58 ` Eduardo Habkost
2018-08-28 14:58 ` [Qemu-devel] " Eduardo Habkost
2018-08-29 16:50 ` Radim Krčmář [this message]
2018-08-29 16:50 ` Radim Krčmář
2018-08-25 12:19 ` [PATCH V4 2/4] target-i386:add coalesced_pio API Peng Hao
2018-08-25 12:19 ` [Qemu-devel] " Peng Hao
2018-08-29 16:43 ` Eduardo Habkost
2018-08-29 16:43 ` [Qemu-devel] " Eduardo Habkost
2018-08-25 12:19 ` [PATCH V4 3/4] target-i386: add rtc 0x70 port as coalesced_pio Peng Hao
2018-08-25 12:19 ` [Qemu-devel] " Peng Hao
2018-08-25 12:19 ` [PATCH V4 4/4] target-i386: add i440fx 0xcf8 " Peng Hao
2018-08-25 12:19 ` [Qemu-devel] " Peng Hao
2018-08-25 23:29 ` Liran Alon
2018-08-25 23:29 ` [Qemu-devel] " Liran Alon
2018-08-28 14:57 ` [PATCH V4 0/4] introduce coalesced pio support Eduardo Habkost
2018-08-28 14:57 ` [Qemu-devel] " 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=20180829165053.GA19438@flask \
--to=rkrcmar@redhat.com \
--cc=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=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 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.