From: Sasha Levin <levinsasha928@gmail.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>,
Jan Kiszka <jan.kiszka@siemens.com>,
Gleb Natapov <gleb@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v7] kvm: notify host when the guest is panicked
Date: Sat, 21 Jul 2012 12:50:17 +0200 [thread overview]
Message-ID: <500A8969.1040300@gmail.com> (raw)
In-Reply-To: <500A565A.8080403@cn.fujitsu.com>
On 07/21/2012 09:12 AM, Wen Congyang wrote:
> +#define KVM_PV_PORT (0x505UL)
> +
> #ifdef __KERNEL__
> #include <asm/processor.h>
>
> @@ -221,6 +223,11 @@ static inline void kvm_disable_steal_time(void)
> }
> #endif
>
> +static inline unsigned int kvm_arch_pv_features(void)
> +{
> + return inl(KVM_PV_PORT);
> +}
> +
Why is this safe?
I'm not sure you can just pick any ioport you'd like and use it.
WARNING: multiple messages have this Message-ID (diff)
From: Sasha Levin <levinsasha928@gmail.com>
To: Wen Congyang <wency@cn.fujitsu.com>
Cc: Gleb Natapov <gleb@redhat.com>, kvm list <kvm@vger.kernel.org>,
Jan Kiszka <jan.kiszka@siemens.com>,
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 v7] kvm: notify host when the guest is panicked
Date: Sat, 21 Jul 2012 12:50:17 +0200 [thread overview]
Message-ID: <500A8969.1040300@gmail.com> (raw)
In-Reply-To: <500A565A.8080403@cn.fujitsu.com>
On 07/21/2012 09:12 AM, Wen Congyang wrote:
> +#define KVM_PV_PORT (0x505UL)
> +
> #ifdef __KERNEL__
> #include <asm/processor.h>
>
> @@ -221,6 +223,11 @@ static inline void kvm_disable_steal_time(void)
> }
> #endif
>
> +static inline unsigned int kvm_arch_pv_features(void)
> +{
> + return inl(KVM_PV_PORT);
> +}
> +
Why is this safe?
I'm not sure you can just pick any ioport you'd like and use it.
next prev parent reply other threads:[~2012-07-21 10:50 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-21 7:12 [PATCH v7] kvm: notify host when the guest is panicked Wen Congyang
2012-07-21 7:12 ` [Qemu-devel] " Wen Congyang
2012-07-21 7:14 ` [PATCH 1/6 v7] start vm after reseting it Wen Congyang
2012-07-21 7:14 ` [Qemu-devel] " Wen Congyang
2012-07-21 7:14 ` [PATCH 2/6 v7] kvm: Update kernel headers Wen Congyang
2012-07-21 7:14 ` [Qemu-devel] " Wen Congyang
2012-07-21 7:15 ` [PATCH 3/6 v7] add a new runstate: RUN_STATE_GUEST_PANICKED Wen Congyang
2012-07-21 7:15 ` [Qemu-devel] " Wen Congyang
2012-07-21 7:16 ` [PATCH 4/6 v7] add a new qevent: QEVENT_GUEST_PANICKED Wen Congyang
2012-07-21 7:16 ` [Qemu-devel] " Wen Congyang
2012-07-21 7:16 ` [PATCH 5/6 v7] introduce a new qom device to deal with panicked event Wen Congyang
2012-07-21 7:16 ` [Qemu-devel] " Wen Congyang
2012-07-21 7:19 ` [PATCH 6/6 v7] allow the user to disable pv event support Wen Congyang
2012-07-21 7:19 ` [Qemu-devel] " Wen Congyang
2012-07-21 7:19 ` [PATCH v7] kvm: notify host when the guest is panicked Jan Kiszka
2012-07-21 7:19 ` [Qemu-devel] " Jan Kiszka
2012-07-21 7:19 ` Jan Kiszka
2012-07-21 8:41 ` Wen Congyang
2012-07-21 8:41 ` [Qemu-devel] " Wen Congyang
2012-07-21 8:41 ` Wen Congyang
2012-07-21 8:44 ` [PATCH v7.5] " Wen Congyang
2012-07-21 8:44 ` [Qemu-devel] " Wen Congyang
2012-07-22 11:39 ` Sasha Levin
2012-07-22 11:39 ` [Qemu-devel] " Sasha Levin
2012-07-22 11:39 ` Sasha Levin
2012-07-22 19:14 ` Anthony Liguori
2012-07-22 19:14 ` Anthony Liguori
2012-07-22 20:03 ` Sasha Levin
2012-07-22 20:03 ` [Qemu-devel] " Sasha Levin
2012-07-22 20:03 ` Sasha Levin
2012-07-22 22:36 ` Anthony Liguori
2012-07-22 22:36 ` [Qemu-devel] " Anthony Liguori
2012-07-22 22:36 ` Anthony Liguori
2012-07-22 23:50 ` Sasha Levin
2012-07-22 23:50 ` [Qemu-devel] " Sasha Levin
2012-07-22 23:50 ` Sasha Levin
2012-07-23 2:08 ` Wen Congyang
2012-07-23 2:08 ` [Qemu-devel] " Wen Congyang
2012-07-23 2:08 ` Wen Congyang
2012-07-23 2:07 ` Wen Congyang
2012-07-23 2:07 ` [Qemu-devel] " Wen Congyang
2012-07-23 2:07 ` Wen Congyang
2012-07-21 10:50 ` Sasha Levin [this message]
2012-07-21 10:50 ` [Qemu-devel] [PATCH v7] " Sasha Levin
2012-07-22 19:22 ` Anthony Liguori
2012-07-22 19:22 ` [Qemu-devel] " Anthony Liguori
2012-07-22 19:22 ` Anthony Liguori
2012-07-22 20:19 ` Sasha Levin
2012-07-22 20:19 ` [Qemu-devel] " Sasha Levin
2012-07-22 20:19 ` Sasha Levin
2012-07-22 20:31 ` Sasha Levin
2012-07-22 20:31 ` [Qemu-devel] " Sasha Levin
2012-07-22 20:31 ` Sasha Levin
2012-07-22 22:29 ` Anthony Liguori
2012-07-22 22:29 ` [Qemu-devel] " Anthony Liguori
2012-07-22 22:29 ` Anthony Liguori
2012-07-22 23:35 ` Sasha Levin
2012-07-22 23:35 ` [Qemu-devel] " Sasha Levin
2012-07-22 23:35 ` Sasha Levin
2012-07-22 22:20 ` Anthony Liguori
2012-07-22 22:20 ` [Qemu-devel] " Anthony Liguori
2012-07-22 22:20 ` Anthony Liguori
2012-07-23 6:27 ` Wen Congyang
2012-07-23 6:27 ` 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=500A8969.1040300@gmail.com \
--to=levinsasha928@gmail.com \
--cc=avi@redhat.com \
--cc=berrange@redhat.com \
--cc=gleb@redhat.com \
--cc=jan.kiszka@siemens.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.