From: Jan Kiszka <jan.kiszka@siemens.com>
To: Wen Congyang <wency@cn.fujitsu.com>
Cc: kvm list <kvm@vger.kernel.org>,
qemu-devel <qemu-devel@nongnu.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Avi Kivity <avi@redhat.com>,
"Daniel P. Berrange" <berrange@redhat.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Gleb Natapov <gleb@redhat.com>
Subject: Re: [PATCH 2/7 v6] update linux headers
Date: Fri, 06 Jul 2012 13:16:35 +0200 [thread overview]
Message-ID: <4FF6C913.5080808@siemens.com> (raw)
In-Reply-To: <4FF6C2E2.5020608@cn.fujitsu.com>
On 2012-07-06 12:50, Wen Congyang wrote:
> At 07/06/2012 06:25 PM, Jan Kiszka Wrote:
>> On 2012-07-06 11:38, Wen Congyang wrote:
>>> Signed-off-by: Wen Congyang <wency@cn.fujitsu.com>
>>
>> Which kvm.git hash is this referring? Please state this to avoid that we
>> are merging support for kernel features that are still under review.
>
> The following kvm.git:
> http://git.kernel.org/?p=virt/kvm/kvm.git;a=summary
>
> I apply my kvm's patch, and use ./scripts/update-linux-headers.sh to
> generate this patch.
OK, means the feature is not yet upstream. So this series is for
reference and early review until the kernel interface is accepted. I
personally push my kernel bits first before suggesting the userspace
parts. Avoids duplicate work if the former changes again during review.
Jan
--
Siemens AG, Corporate Technology, CT RTC ITP SDP-DE
Corporate Competence Center Embedded Linux
WARNING: multiple messages have this Message-ID (diff)
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Wen Congyang <wency@cn.fujitsu.com>
Cc: Gleb Natapov <gleb@redhat.com>, kvm list <kvm@vger.kernel.org>,
qemu-devel <qemu-devel@nongnu.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Avi Kivity <avi@redhat.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Subject: Re: [Qemu-devel] [PATCH 2/7 v6] update linux headers
Date: Fri, 06 Jul 2012 13:16:35 +0200 [thread overview]
Message-ID: <4FF6C913.5080808@siemens.com> (raw)
In-Reply-To: <4FF6C2E2.5020608@cn.fujitsu.com>
On 2012-07-06 12:50, Wen Congyang wrote:
> At 07/06/2012 06:25 PM, Jan Kiszka Wrote:
>> On 2012-07-06 11:38, Wen Congyang wrote:
>>> Signed-off-by: Wen Congyang <wency@cn.fujitsu.com>
>>
>> Which kvm.git hash is this referring? Please state this to avoid that we
>> are merging support for kernel features that are still under review.
>
> The following kvm.git:
> http://git.kernel.org/?p=virt/kvm/kvm.git;a=summary
>
> I apply my kvm's patch, and use ./scripts/update-linux-headers.sh to
> generate this patch.
OK, means the feature is not yet upstream. So this series is for
reference and early review until the kernel interface is accepted. I
personally push my kernel bits first before suggesting the userspace
parts. Avoids duplicate work if the former changes again during review.
Jan
--
Siemens AG, Corporate Technology, CT RTC ITP SDP-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2012-07-06 11:16 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-06 9:36 [PATCH v6] kvm: notify host when the guest is panicked Wen Congyang
2012-07-06 9:36 ` [Qemu-devel] " Wen Congyang
2012-07-06 9:38 ` [PATCH 1/7 v6] start vm after reseting it Wen Congyang
2012-07-06 9:38 ` [Qemu-devel] " Wen Congyang
2012-07-06 9:38 ` [PATCH 2/7 v6] update linux headers Wen Congyang
2012-07-06 9:38 ` [Qemu-devel] " Wen Congyang
2012-07-06 10:25 ` Jan Kiszka
2012-07-06 10:25 ` [Qemu-devel] " Jan Kiszka
2012-07-06 10:50 ` Wen Congyang
2012-07-06 10:50 ` [Qemu-devel] " Wen Congyang
2012-07-06 10:50 ` Wen Congyang
2012-07-06 10:55 ` [Qemu-devel] " 陳韋任 (Wei-Ren Chen)
2012-07-06 10:55 ` 陳韋任 (Wei-Ren Chen)
2012-07-06 11:16 ` Jan Kiszka [this message]
2012-07-06 11:16 ` Jan Kiszka
2012-07-07 14:35 ` Paul Gortmaker
2012-07-07 14:35 ` [Qemu-devel] " Paul Gortmaker
2012-07-06 9:39 ` [PATCH 3/7 v6] add a new runstate: RUN_STATE_GUEST_PANICKED Wen Congyang
2012-07-06 9:39 ` [Qemu-devel] " Wen Congyang
2012-07-06 9:40 ` [PATCH 4/7 v6] add a new qevent: QEVENT_GUEST_PANICKED Wen Congyang
2012-07-06 9:40 ` [Qemu-devel] " Wen Congyang
2012-07-06 9:41 ` [PATCH 5/7 v6] introduce a new qom device to deal with panicked event Wen Congyang
2012-07-06 9:41 ` [Qemu-devel] " Wen Congyang
2012-07-06 11:05 ` Jan Kiszka
2012-07-06 11:05 ` [Qemu-devel] " Jan Kiszka
2012-07-06 11:05 ` Jan Kiszka
2012-07-18 1:54 ` Wen Congyang
2012-07-18 1:54 ` [Qemu-devel] " Wen Congyang
2012-07-18 9:19 ` Jan Kiszka
2012-07-18 9:19 ` [Qemu-devel] " Jan Kiszka
2012-07-18 9:25 ` Jan Kiszka
2012-07-18 9:25 ` [Qemu-devel] " Jan Kiszka
2012-07-06 9:41 ` [PATCH 6/7 v6] deal with guest panicked event accoring to -onpanic parameter Wen Congyang
2012-07-06 9:41 ` [Qemu-devel] " Wen Congyang
2012-07-06 11:12 ` Jan Kiszka
2012-07-06 11:12 ` [Qemu-devel] " Jan Kiszka
2012-07-06 11:12 ` Jan Kiszka
2012-07-06 9:41 ` [PATCH 7/7 v6] deal with panicked event accoring to '-machine panic_action=action' Wen Congyang
2012-07-06 9:41 ` [Qemu-devel] " Wen Congyang
2012-07-06 11:09 ` Jan Kiszka
2012-07-06 11:09 ` [Qemu-devel] " Jan Kiszka
2012-07-06 11:09 ` Jan Kiszka
2012-07-09 10:44 ` Wen Congyang
2012-07-09 10:44 ` [Qemu-devel] " Wen Congyang
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=4FF6C913.5080808@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=avi@redhat.com \
--cc=berrange@redhat.com \
--cc=gleb@redhat.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=wency@cn.fujitsu.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.