On 25/02/14 18:25, Cornelia Huck wrote:
+int kvm_s390_io_adapter_map(uint32_t id, uint64_t map_addr, bool do_map)
+{
+struct kvm_s390_io_adapter_req req = {
+.id = id,
+.type = do_map ? KVM_S390_IO_ADAPTER_MAP : KVM_S390_IO_ADAPTER_UNMAP,
+.addr = map_addr,
+
On Wed, 26 Feb 2014 09:29:12 +0100
Christian Borntraeger borntrae...@de.ibm.com wrote:
On 25/02/14 18:25, Cornelia Huck wrote:
+int kvm_s390_io_adapter_map(uint32_t id, uint64_t map_addr, bool do_map)
+{
+struct kvm_s390_io_adapter_req req = {
+.id = id,
+.type =
Il 26/02/2014 02:44, Marcelo Tosatti ha scritto:
emulator_cmpxchg_emulated writes to guest memory, therefore it should
updated the dirty bitmap accordingly.
Signed-off-by: Marcelo Tosatti mtosa...@redhat.com
diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
index 39c28f09..29db96d 100644
On Wed, Feb 26, 2014 at 03:11:21PM +0800, Jason Wang wrote:
On 02/26/2014 02:32 PM, Qin Chuanyu wrote:
On 2014/2/26 13:53, Jason Wang wrote:
On 02/25/2014 09:57 PM, Michael S. Tsirkin wrote:
On Tue, Feb 25, 2014 at 02:53:58PM +0800, Jason Wang wrote:
We used to stop the handling of tx when
guest kick host base on avail_ring flags value and get perfermance
improved, vhost_zerocopy_callback could do the same thing. As
virtqueue_enable_cb need one more check after modifying the value of
avail_ring flags, vhost also need do the same thing after
vhost_enable_notify.
test result list as
On 2014/2/26 17:20, Qin Chuanyu wrote:
guest kick host base on avail_ring flags value and get perfermance
improved, vhost_zerocopy_callback could do the same thing. As
virtqueue_enable_cb need one more check after modifying the value of
avail_ring flags, vhost also need do the same thing after
Il 26/02/2014 03:22, Marcelo Tosatti ha scritto:
Rather than fall back to TCG (so the user has to discover
whats happening, in case of no access to qemu stdout/stderr).
Signed-off-by: Marcelo Tosatti mtosa...@redhat.com
diff --git a/kvm-all.c b/kvm-all.c
index 3937754..3f6841d 100644
---
Il 25/02/2014 04:29, Luiz Capitulino ha scritto:
I got a report of someone trying to run tests with a large amount of
RAM (4GB), which broke the guest as free_memory() function (called
by setup_vm()) will override the PCI hole.
Let's document memory constraints so that people don't do that.
Currently each MOV to a debug register causes a debug exit. Add a
testcase to track upcoming improvements.
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
x86/vmexit.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/x86/vmexit.c b/x86/vmexit.c
index 7e9af15..cc24738 100644
---
Please see MAINTAINERS and copy all relevant lists.
On Wed, Feb 26, 2014 at 05:20:09PM +0800, Qin Chuanyu wrote:
guest kick host base on avail_ring flags value and get perfermance
typo
improved, vhost_zerocopy_callback could do the same thing. As
virtqueue_enable_cb need one more check after
XSAVE support for KVM is already using host_xcr0 KVM_SUPPORTED_XCR0 as
a dynamic version of KVM_SUPPORTED_XCR0.
However, this is not enough because the MPX bits should not be presented
to the guest unless kvm_x86_ops confirms the support. So, replace all
instances of host_xcr0
This is simple to do, the host BNDCFGS is either 0 or the guest value.
However, both controls have to be present. We cannot provide MPX if
we only have one of the load BNDCFGS or clear BNDCFGS controls.
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
arch/x86/kvm/vmx.c | 17
Here are the patches I mentioned while reviewing Liu Jinsong's MPX
series.
Patch 1 is a further cleanup of xcr0 handling, and patch 2 introduces
nested virtualization support for MPX.
Please review.
Thanks,
Paolo
Paolo Bonzini (2):
KVM: x86: introduce kvm_supported_xcr0()
KVM: x86: Add
Geachte Webmail Gebruiker,
Uw twee inkomende mails hangende toestand geplaatst als gevolg van de recente
upgrade in onze database.
in volgorde te ontvangen uw berichten KLIK
HIERhttp://goorsoicuesaeorusdoisda.webs.com/
Login met uw juiste Webmail informatie en wachten op antwoordt van onze
Paolo,
here is the reworked yield heuristics series against kvm/queue with
your suggested changes.
Attached is a minimized testcase that reproduces the performance
win (runtime 0:50 instead of 1:00). The constants and the setup
seem a bit artificial but these seem to reproduce the problem on my
From: Michael Mueller m...@linux.vnet.ibm.com
Use the arch specific function kvm_arch_vcpu_runnable() to add a further
criterium to identify a suitable vcpu to yield to during undirected yield
processing.
Signed-off-by: Michael Mueller m...@linux.vnet.ibm.com
Reviewed-by: Christian Borntraeger
From: Michael Mueller m...@linux.vnet.ibm.com
A vcpu is defined to be runnable if an interrupt is pending.
Signed-off-by: Michael Mueller m...@linux.vnet.ibm.com
Reviewed-by: Christian Borntraeger borntrae...@de.ibm.com
Signed-off-by: Christian Borntraeger borntrae...@de.ibm.com
---
From: Michael Mueller m...@linux.vnet.ibm.com
Commit kvm: Record the preemption status of vcpus using preempt notifiers
caused a performance regression on s390. It turned out that in the case that
if a former sleeping cpu, that was woken up, this cpu is not a yield candidate
since it gave up the
When not running in guest-debug mode, the guest controls the debug
registers and having to take an exit for each DR access is a waste
of time. If the guest gets into a state where each context switch
causes DR to be saved and restored, this can take away as much as 40%
of the execution time from
When not running in guest-debug mode (i.e. the guest controls the debug
registers, having to take an exit for each DR access is a waste of time.
If the guest gets into a state where each context switch causes DR to be
saved and restored, this can take away as much as 40% of the execution
time from
The next patch will add another bit that we can test with the
same if.
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
arch/x86/include/asm/kvm_host.h | 6 +-
arch/x86/kvm/x86.c | 6 --
2 files changed, 9 insertions(+), 3 deletions(-)
diff --git
Currently, this works even if the bit is not in min, because the bit is always
set in MSR_IA32_VMX_ENTRY_CTLS. Mention it for the sake of documentation, and
to avoid surprises if we later switch to MSR_IA32_VMX_TRUE_ENTRY_CTLS.
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
Alex Williamson reported that a Windows game does something weird that
makes the guest save and restore debug registers on each context switch.
This cause several hundred thousands vmexits per second, and basically
cuts performance in half when running under KVM.
However, when not running in
Il 26/02/2014 16:14, Christian Borntraeger ha scritto:
Paolo,
here is the reworked yield heuristics series against kvm/queue with
your suggested changes.
Attached is a minimized testcase that reproduces the performance
win (runtime 0:50 instead of 1:00). The constants and the setup
seem a bit
This is simple to do, the host BNDCFGS is either 0 or the guest value.
However, both controls have to be present. We cannot provide MPX if
we only have one of the load BNDCFGS or clear BNDCFGS controls.
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
arch/x86/kvm/vmx.c | 17
XSAVE support for KVM is already using host_xcr0 KVM_SUPPORTED_XCR0 as
a dynamic version of KVM_SUPPORTED_XCR0.
However, this is not enough because the MPX bits should not be presented
to the guest unless kvm_x86_ops confirms the support. So, replace all
instances of host_xcr0
Here are the patches I mentioned while reviewing Liu Jinsong's MPX
series.
Patch 1 is a further cleanup of xcr0 handling, and patch 2 introduces
nested virtualization support for MPX.
Please review.
Thanks,
Paolo
Paolo Bonzini (2):
KVM: x86: introduce kvm_supported_xcr0()
KVM: x86: Add
On Wed, 2014-02-26 at 16:49 +0100, Paolo Bonzini wrote:
Alex Williamson reported that a Windows game does something weird that
makes the guest save and restore debug registers on each context switch.
This cause several hundred thousands vmexits per second, and basically
cuts performance in
commit 0061d53daf26f introduced a mechanism to execute a global clock
update for a vm. We can apply this periodically in order to propagate
host NTP corrections. Also, if all vcpus of a vm are pinned, then
without an additional trigger, no guest NTP corrections can propagate
either, as the current
When we update a vcpu's local clock it may pick up an NTP correction.
We can't wait an indeterminate amount of time for other vcpus to pick
up that correction, so commit 0061d53daf26f introduced a global clock
update. However, we can't request a global clock update on every vcpu
load either (which
This patch series addresses two issues with global clock updates.
The first fixes a bug found on hosts that have a tsc marked as
unstable. As global clock updates get triggered on every vcpu load
in these cases, guests with a large number of vcpus have their
progress nearly halted. The fix for
ARM VM System Specification
===
Goal
The goal of this spec is to allow suitably-built OS images to run on
all ARM virtualization solutions, such as KVM or Xen.
Recommendations in this spec are valid for aarch32 and aarch64 alike, and
they aim to be hypervisor
Commit 1fcf7ce0c602 (arm: kvm: implement CPU PM notifier) added
support for CPU power-management, using a cpu_notifier to re-init
KVM on a CPU that entered CPU idle.
The code assumed that a CPU entering idle would actually be powered
off, loosing its state entierely, and would then need to be
Hi Christoffer,
On 02/26/2014 01:34 PM, Christoffer Dall wrote:
ARM VM System Specification
===
Goal
The goal of this spec is to allow suitably-built OS images to run on
all ARM virtualization solutions, such as KVM or Xen.
Would you consider including
Hi,
I was looking at a bug report[1] about a regression on nested VMX that started
with kernel v3.13 (same issue still existed with v3.14-rc4). The problem shows
up when running a v3.13 kernel in L0 and then trying to launch a L2 (L1 was
either a v3.2 kernel or v3.13, so seemed to have no
On Wed, Feb 26, 2014 at 02:27:40PM -0500, Christopher Covington wrote:
Hi Christoffer,
On 02/26/2014 01:34 PM, Christoffer Dall wrote:
ARM VM System Specification
===
Goal
The goal of this spec is to allow suitably-built OS images to run on
all ARM
On Wednesday 26 February 2014 10:34:54 Christoffer Dall wrote:
ARM VM System Specification
===
Goal
The goal of this spec is to allow suitably-built OS images to run on
all ARM virtualization solutions, such as KVM or Xen.
Recommendations in this spec are
On Wed, Feb 26, 2014 at 08:55:58PM +0100, Arnd Bergmann wrote:
On Wednesday 26 February 2014 10:34:54 Christoffer Dall wrote:
ARM VM System Specification
===
Goal
The goal of this spec is to allow suitably-built OS images to run on
all ARM
Il 26/02/2014 20:55, Arnd Bergmann ha scritto:
For more information about UEFI and ACPI booting, see [4] and [5].
What's the point of having ACPI in a virtual machine? You wouldn't
need to abstract any of the hardware in AML since you already know
what the virtual hardware is, so I can't see
On 26 February 2014 20:19, Paolo Bonzini pbonz...@redhat.com wrote:
Il 26/02/2014 20:55, Arnd Bergmann ha scritto:
Did you notice we are removing mach-virt now? Probably no point
mentioning it here.
Peter, do we still want mach-virt support in QEMU then?
Yes, it will be about the only thing
On Wednesday 26 February 2014 12:05:37 Christoffer Dall wrote:
On Wed, Feb 26, 2014 at 08:55:58PM +0100, Arnd Bergmann wrote:
On Wednesday 26 February 2014 10:34:54 Christoffer Dall wrote:
The most common response I've been getting so far is that people
generally want their VMs to look
Il 26/02/2014 20:43, Stefan Bader ha scritto:
Hi,
I was looking at a bug report[1] about a regression on nested VMX that started
with kernel v3.13 (same issue still existed with v3.14-rc4). The problem shows
up when running a v3.13 kernel in L0 and then trying to launch a L2 (L1 was
either a
On 26.02.2014 21:25, Paolo Bonzini wrote:
Il 26/02/2014 20:43, Stefan Bader ha scritto:
Hi,
I was looking at a bug report[1] about a regression on nested VMX that
started
with kernel v3.13 (same issue still existed with v3.14-rc4). The problem
shows
up when running a v3.13 kernel in L0
On Wed, Feb 26, 2014 at 07:15:11PM +0100, Andrew Jones wrote:
When we update a vcpu's local clock it may pick up an NTP correction.
We can't wait an indeterminate amount of time for other vcpus to pick
up that correction, so commit 0061d53daf26f introduced a global clock
update. However, we
On Wed, Feb 26, 2014 at 07:15:12PM +0100, Andrew Jones wrote:
commit 0061d53daf26f introduced a mechanism to execute a global clock
update for a vm. We can apply this periodically in order to propagate
host NTP corrections. Also, if all vcpus of a vm are pinned, then
without an additional
https://bugzilla.kernel.org/show_bug.cgi?id=69491
--- Comment #7 from Kashyap Chamarthy kashyap...@gmail.com ---
(In reply to Kashyap Chamarthy from comment #6)
[. . .]
I just tested with this Kernel 3.14.0-0.rc1.git4.1.fc21.x86_64 my bare-metal,
booted L1 (running:
Paulo, Gleb,
Can you please queue this as a fix for 3.14?
It fixes an issue that has been introduced during the merge window,
and it would be good to have it plugged quickly.
Ok, I plan to send a pull request on Friday (it should make it in -rc5).
Paolo
--
To unsubscribe from this list:
On Wed, Feb 26, 2014 at 09:27:17PM +0100, Stefan Bader wrote:
On 26.02.2014 21:25, Paolo Bonzini wrote:
[. . .]
I bisected this and ended up on the following commit which, when reverted
made
the launch work again:
Author: Anthoine Bourgeois bourge...@bertin.fr
Date: Wed Nov 13
Christoffer Dall christoffer.d...@linaro.org writes:
Hardware Description
The Linux kernel's proper entry point always takes a pointer to an FDT,
regardless of the boot mechanism, firmware, and hardware description
method. Even on real hardware which only supports ACPI
On Thu, Feb 27, 2014 at 10:05:05AM +1300, Michael Hudson-Doyle wrote:
Christoffer Dall christoffer.d...@linaro.org writes:
Hardware Description
The Linux kernel's proper entry point always takes a pointer to an FDT,
regardless of the boot mechanism, firmware, and
On Wed, Feb 26, 2014 at 08:55:58PM +0100, Arnd Bergmann wrote:
On Wednesday 26 February 2014 10:34:54 Christoffer Dall wrote:
ARM VM System Specification
===
Goal
The goal of this spec is to allow suitably-built OS images to run on
all ARM
On Wed, Feb 26, 2014 at 2:22 PM, Arnd Bergmann a...@arndb.de wrote:
On Wednesday 26 February 2014 12:05:37 Christoffer Dall wrote:
On Wed, Feb 26, 2014 at 08:55:58PM +0100, Arnd Bergmann wrote:
On Wednesday 26 February 2014 10:34:54 Christoffer Dall wrote:
The most common response I've been
On Wed, Feb 26, 2014 at 03:56:02PM -0600, Rob Herring wrote:
On Wed, Feb 26, 2014 at 2:22 PM, Arnd Bergmann a...@arndb.de wrote:
On Wednesday 26 February 2014 12:05:37 Christoffer Dall wrote:
On Wed, Feb 26, 2014 at 08:55:58PM +0100, Arnd Bergmann wrote:
On Wednesday 26 February 2014
On Wed, Feb 26, 2014 at 09:48:43PM +, Leif Lindholm wrote:
On Wed, Feb 26, 2014 at 08:55:58PM +0100, Arnd Bergmann wrote:
On Wednesday 26 February 2014 10:34:54 Christoffer Dall wrote:
ARM VM System Specification
===
Goal
The goal of this spec
Hi Grant,
Thanks for comments,
On Wed, Feb 26, 2014 at 10:35:54PM +, Grant Likely wrote:
On 26 Feb 2014 18:35, Christoffer Dall christoffer.d...@linaro.org
wrote:
ARM VM System Specification
===
Goal
The goal of this spec is to allow
On Wed, Feb 26, 2014 at 1:55 PM, Arnd Bergmann a...@arndb.de wrote:
On Wednesday 26 February 2014 10:34:54 Christoffer Dall wrote:
ARM VM System Specification
===
Goal
The goal of this spec is to allow suitably-built OS images to run on
all ARM virtualization
On 26 February 2014 22:49, Rob Herring robherri...@gmail.com wrote
The SBSA only spec's a very minimal pl011 subset which is only
suitable for early serial output. Not only is there no DMA, but there
are no interrupts and maybe no input.
No interrupts on a UART in a VM (especially an emulated
On Wed, Feb 26, 2014 at 4:54 PM, Peter Maydell peter.mayd...@linaro.org wrote:
On 26 February 2014 22:49, Rob Herring robherri...@gmail.com wrote
The SBSA only spec's a very minimal pl011 subset which is only
suitable for early serial output. Not only is there no DMA, but there
are no
On 02/26/2014 05:49 PM, Rob Herring wrote:
On Wed, Feb 26, 2014 at 1:55 PM, Arnd Bergmann a...@arndb.de wrote:
On Wednesday 26 February 2014 10:34:54 Christoffer Dall wrote:
ARM VM System Specification
===
Goal
The goal of this spec is to allow suitably-built
On 26 February 2014 23:08, Rob Herring robherri...@gmail.com wrote:
On Wed, Feb 26, 2014 at 4:54 PM, Peter Maydell peter.mayd...@linaro.org
wrote:
What does the 8250 have to recommend it over just providing
the PL011?
As I mentioned, it will just work for anything that expects the serial
On 2/26/14 10:34 AM, Christoffer Dall wrote:
ARM VM System Specification
===
See also the thread forked off to the EFI dev list, about using existing
EFI ByteCode (EBC) for this new purpose, especially the informative
reply from Andrew Fish of Apple.com:
On 02/26/2014 05:23 PM, Michael S. Tsirkin wrote:
On Wed, Feb 26, 2014 at 03:11:21PM +0800, Jason Wang wrote:
On 02/26/2014 02:32 PM, Qin Chuanyu wrote:
On 2014/2/26 13:53, Jason Wang wrote:
On 02/25/2014 09:57 PM, Michael S. Tsirkin wrote:
On Tue, Feb 25, 2014 at 02:53:58PM +0800, Jason
On Wed, 26 Feb 2014, Peter Maydell wrote:
On 26 February 2014 23:08, Rob Herring robherri...@gmail.com wrote:
On Wed, Feb 26, 2014 at 4:54 PM, Peter Maydell peter.mayd...@linaro.org
wrote:
What does the 8250 have to recommend it over just providing
the PL011?
As I mentioned, it will
No need to scan the entire VCPU array.
Signed-off-by: Takuya Yoshikawa yoshikawa_takuya...@lab.ntt.co.jp
---
BTW, this looks like hyperv support forces us to stick to the current
implementation which stores VCPUs in an array, or at least something
we can index them; not a good thing.
On Wednesday 26 February 2014, Christoffer Dall wrote:
Personally I'm all for simplicity so I don't want to push any agenda for
ACPI in VMs.
Note that the spec does not mandate the use of ACPI, it just tells you
how to do it if you wish to.
But, we can change the spec to require full FDT
I'm specifically looking for a KVM mailing list that has more
discussions about KVM based solutions and similar, and less development
spam/patches?
Thanks
--
//T
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo
66 matches
Mail list logo
