From: paulmck at linux.ibm.com (Paul E. McKenney)
Subject: [PATCH] rcutorture: Tweak kvm options
Date: Wed, 24 Apr 2019 11:30:39 -0700 [thread overview]
Message-ID: <20190424183039.GA4494@linux.ibm.com> (raw)
In-Reply-To: <20190424103809.GM3923@linux.ibm.com>
On Wed, Apr 24, 2019 at 03:38:09AM -0700, Paul E. McKenney wrote:
> On Wed, Apr 24, 2019 at 09:34:46AM +0200, Sebastian Andrzej Siewior wrote:
> > In one of my rcutorture tests the TSC clocksource got marked unstable
> > due to a large difference in the TSC value. I'm not sure if the guest
> > run for a long time with disabled interrupts or if the host was very
> > busy and didn't schedule the guest for some time.
> > I took a look on the qemu/KVM options and decided to update the options:
> > - Use kvm{32|64} as CPU. We could probably use `host' (like ARM does)
> > for maximum available features but since we don't run any userland I'm
> > not sure if it makes any difference.
> >
> > - Drop the "noapic" option, enable TSC deadline timer. There is no
> > history why the APIC was disabled, I see no reason for it. The
> > deadline timer is probably "nicer".
> >
> > - Additional config options. It ensures that the kernel knowns that it
> > runs as a kvm guest and can use virt devices like the kvm-clock as
> > clocksource. The kvm-clock was the main motivation here.
> >
> > - I didn't add a random HW device. It would make the random device ready
> > earlier (not it doesn't complete the initialisation at all) but I
> > doubt that there is any need for this.
> >
> > Signed-off-by: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
>
> Thank you, Sebastian! Queued for review and testing.
And it doesn't like my (admittedly ancient) QEMU, complaining about not
knowing about "x2apic=on,tsc-deadline=on,hypervisor=on,tsc_adjust=on".
If I remove these, it works. I will be upgrading soon (famous last
words), so what I am going to do is queue the following separate
not-for-upstream patch that makes it work on my setup.
Thanx, Paul
------------------------------------------------------------------------
commit d33dffe7d1f05adfc798836a9d30b9f6bf69635d
Author: Paul E. McKenney <paulmck at linux.ibm.com>
Date: Wed Apr 24 05:20:07 2019 -0700
EXP torture: Hack patch to support ancient QEMU
To be removed before upstreaming or when Paul gets his QEMU act together,
whichever comes first. ;-)
Signed-off-by: Paul E. McKenney <paulmck at linux.ibm.com>
diff --git a/tools/testing/selftests/rcutorture/bin/functions.sh b/tools/testing/selftests/rcutorture/bin/functions.sh
index be3c5c73d7e7..c3a49fb4d6f6 100644
--- a/tools/testing/selftests/rcutorture/bin/functions.sh
+++ b/tools/testing/selftests/rcutorture/bin/functions.sh
@@ -203,7 +203,7 @@ identify_qemu_args () {
case "$1" in
qemu-system-x86_64|qemu-system-i386)
echo -machine q35,accel=kvm
- echo -cpu ${KVM_CPU},x2apic=on,tsc-deadline=on,hypervisor=on,tsc_adjust=on
+ echo -cpu ${KVM_CPU}
;;
qemu-system-aarch64)
echo -machine virt,gic-version=host -cpu host
WARNING: multiple messages have this Message-ID (diff)
From: paulmck@linux.ibm.com (Paul E. McKenney)
Subject: [PATCH] rcutorture: Tweak kvm options
Date: Wed, 24 Apr 2019 11:30:39 -0700 [thread overview]
Message-ID: <20190424183039.GA4494@linux.ibm.com> (raw)
Message-ID: <20190424183039.DQQaX4gCm3LWExUk8NT_ViuS_Eveu5MrroCOOT0aIs8@z> (raw)
In-Reply-To: <20190424103809.GM3923@linux.ibm.com>
On Wed, Apr 24, 2019@03:38:09AM -0700, Paul E. McKenney wrote:
> On Wed, Apr 24, 2019@09:34:46AM +0200, Sebastian Andrzej Siewior wrote:
> > In one of my rcutorture tests the TSC clocksource got marked unstable
> > due to a large difference in the TSC value. I'm not sure if the guest
> > run for a long time with disabled interrupts or if the host was very
> > busy and didn't schedule the guest for some time.
> > I took a look on the qemu/KVM options and decided to update the options:
> > - Use kvm{32|64} as CPU. We could probably use `host' (like ARM does)
> > for maximum available features but since we don't run any userland I'm
> > not sure if it makes any difference.
> >
> > - Drop the "noapic" option, enable TSC deadline timer. There is no
> > history why the APIC was disabled, I see no reason for it. The
> > deadline timer is probably "nicer".
> >
> > - Additional config options. It ensures that the kernel knowns that it
> > runs as a kvm guest and can use virt devices like the kvm-clock as
> > clocksource. The kvm-clock was the main motivation here.
> >
> > - I didn't add a random HW device. It would make the random device ready
> > earlier (not it doesn't complete the initialisation at all) but I
> > doubt that there is any need for this.
> >
> > Signed-off-by: Sebastian Andrzej Siewior <bigeasy at linutronix.de>
>
> Thank you, Sebastian! Queued for review and testing.
And it doesn't like my (admittedly ancient) QEMU, complaining about not
knowing about "x2apic=on,tsc-deadline=on,hypervisor=on,tsc_adjust=on".
If I remove these, it works. I will be upgrading soon (famous last
words), so what I am going to do is queue the following separate
not-for-upstream patch that makes it work on my setup.
Thanx, Paul
------------------------------------------------------------------------
commit d33dffe7d1f05adfc798836a9d30b9f6bf69635d
Author: Paul E. McKenney <paulmck at linux.ibm.com>
Date: Wed Apr 24 05:20:07 2019 -0700
EXP torture: Hack patch to support ancient QEMU
To be removed before upstreaming or when Paul gets his QEMU act together,
whichever comes first. ;-)
Signed-off-by: Paul E. McKenney <paulmck at linux.ibm.com>
diff --git a/tools/testing/selftests/rcutorture/bin/functions.sh b/tools/testing/selftests/rcutorture/bin/functions.sh
index be3c5c73d7e7..c3a49fb4d6f6 100644
--- a/tools/testing/selftests/rcutorture/bin/functions.sh
+++ b/tools/testing/selftests/rcutorture/bin/functions.sh
@@ -203,7 +203,7 @@ identify_qemu_args () {
case "$1" in
qemu-system-x86_64|qemu-system-i386)
echo -machine q35,accel=kvm
- echo -cpu ${KVM_CPU},x2apic=on,tsc-deadline=on,hypervisor=on,tsc_adjust=on
+ echo -cpu ${KVM_CPU}
;;
qemu-system-aarch64)
echo -machine virt,gic-version=host -cpu host
WARNING: multiple messages have this Message-ID (diff)
From: "Paul E. McKenney" <paulmck@linux.ibm.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linux-kselftest@vger.kernel.org, rcu@vger.kernel.org,
Josh Triplett <josh@joshtriplett.org>,
Steven Rostedt <rostedt@goodmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Lai Jiangshan <jiangshanlai@gmail.com>,
Shuah Khan <shuah@kernel.org>
Subject: Re: [PATCH] rcutorture: Tweak kvm options
Date: Wed, 24 Apr 2019 11:30:39 -0700 [thread overview]
Message-ID: <20190424183039.GA4494@linux.ibm.com> (raw)
In-Reply-To: <20190424103809.GM3923@linux.ibm.com>
On Wed, Apr 24, 2019 at 03:38:09AM -0700, Paul E. McKenney wrote:
> On Wed, Apr 24, 2019 at 09:34:46AM +0200, Sebastian Andrzej Siewior wrote:
> > In one of my rcutorture tests the TSC clocksource got marked unstable
> > due to a large difference in the TSC value. I'm not sure if the guest
> > run for a long time with disabled interrupts or if the host was very
> > busy and didn't schedule the guest for some time.
> > I took a look on the qemu/KVM options and decided to update the options:
> > - Use kvm{32|64} as CPU. We could probably use `host' (like ARM does)
> > for maximum available features but since we don't run any userland I'm
> > not sure if it makes any difference.
> >
> > - Drop the "noapic" option, enable TSC deadline timer. There is no
> > history why the APIC was disabled, I see no reason for it. The
> > deadline timer is probably "nicer".
> >
> > - Additional config options. It ensures that the kernel knowns that it
> > runs as a kvm guest and can use virt devices like the kvm-clock as
> > clocksource. The kvm-clock was the main motivation here.
> >
> > - I didn't add a random HW device. It would make the random device ready
> > earlier (not it doesn't complete the initialisation at all) but I
> > doubt that there is any need for this.
> >
> > Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
>
> Thank you, Sebastian! Queued for review and testing.
And it doesn't like my (admittedly ancient) QEMU, complaining about not
knowing about "x2apic=on,tsc-deadline=on,hypervisor=on,tsc_adjust=on".
If I remove these, it works. I will be upgrading soon (famous last
words), so what I am going to do is queue the following separate
not-for-upstream patch that makes it work on my setup.
Thanx, Paul
------------------------------------------------------------------------
commit d33dffe7d1f05adfc798836a9d30b9f6bf69635d
Author: Paul E. McKenney <paulmck@linux.ibm.com>
Date: Wed Apr 24 05:20:07 2019 -0700
EXP torture: Hack patch to support ancient QEMU
To be removed before upstreaming or when Paul gets his QEMU act together,
whichever comes first. ;-)
Signed-off-by: Paul E. McKenney <paulmck@linux.ibm.com>
diff --git a/tools/testing/selftests/rcutorture/bin/functions.sh b/tools/testing/selftests/rcutorture/bin/functions.sh
index be3c5c73d7e7..c3a49fb4d6f6 100644
--- a/tools/testing/selftests/rcutorture/bin/functions.sh
+++ b/tools/testing/selftests/rcutorture/bin/functions.sh
@@ -203,7 +203,7 @@ identify_qemu_args () {
case "$1" in
qemu-system-x86_64|qemu-system-i386)
echo -machine q35,accel=kvm
- echo -cpu ${KVM_CPU},x2apic=on,tsc-deadline=on,hypervisor=on,tsc_adjust=on
+ echo -cpu ${KVM_CPU}
;;
qemu-system-aarch64)
echo -machine virt,gic-version=host -cpu host
next prev parent reply other threads:[~2019-04-24 18:30 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-24 7:34 [PATCH] rcutorture: Tweak kvm options bigeasy
2019-04-24 7:34 ` Sebastian Andrzej Siewior
2019-04-24 7:34 ` Sebastian Andrzej Siewior
2019-04-24 10:38 ` paulmck
2019-04-24 10:38 ` Paul E. McKenney
2019-04-24 10:38 ` Paul E. McKenney
2019-04-24 18:30 ` paulmck [this message]
2019-04-24 18:30 ` Paul E. McKenney
2019-04-24 18:30 ` Paul E. McKenney
2019-04-25 19:46 ` paulmck
2019-04-25 19:46 ` Paul E. McKenney
2019-04-25 19:46 ` Paul E. McKenney
2019-04-26 10:54 ` bigeasy
2019-04-26 10:54 ` Sebastian Andrzej Siewior
2019-04-26 10:54 ` Sebastian Andrzej Siewior
2019-04-26 13:50 ` paulmck
2019-04-26 13:50 ` Paul E. McKenney
2019-04-26 13:50 ` Paul E. McKenney
2019-04-29 8:19 ` bigeasy
2019-04-29 8:19 ` Sebastian Andrzej Siewior
2019-04-29 8:19 ` Sebastian Andrzej Siewior
2019-04-29 14:49 ` paulmck
2019-04-29 14:49 ` Paul E. McKenney
2019-04-29 14:49 ` Paul E. McKenney
2019-04-29 15:06 ` paulmck
2019-04-29 15:06 ` Paul E. McKenney
2019-04-29 15:06 ` Paul E. McKenney
2019-05-02 18:41 ` paulmck
2019-05-02 18:41 ` Paul E. McKenney
2019-05-02 18:41 ` Paul E. McKenney
2019-05-03 7:26 ` bigeasy
2019-05-03 7:26 ` Sebastian Andrzej Siewior
2019-05-03 7:26 ` Sebastian Andrzej Siewior
2019-04-25 16:45 ` joel
2019-04-25 16:45 ` Joel Fernandes
2019-04-25 16:45 ` Joel Fernandes
2019-04-25 17:13 ` bigeasy
2019-04-25 17:13 ` Sebastian Andrzej Siewior
2019-04-25 17:13 ` Sebastian Andrzej Siewior
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=20190424183039.GA4494@linux.ibm.com \
--to=unknown@example.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.