From: Bernhard Kohl bernhard.k...@nsn.com
With the latest git versions, e.g. 1.7.2.3, git still prints out
the tag info in addition to the requested format. So let's simply
fetch the first line from the output.
In addition I use the --pretty option instead of --format which
is not recognized in
From: Bernhard Kohl bernhard.k...@nsn.com
This is necessary because during reboot of a VM the assigned devices
continue DMA transfers which causes memory corruption.
Acked-by: Alex Williamson alex.william...@redhat.com
Acked-by: Jan Kiszka jan.kis...@siemens.com
Signed-off-by: Thomas Ostler
From: Alex Williamson alex.william...@redhat.com
Use register_device_unmigratable() to declare ourselves as
non-migratable.
Signed-off-by: Alex Williamson alex.william...@redhat.com
Signed-off-by: Marcelo Tosatti mtosa...@redhat.com
diff --git a/hw/device-assignment.c b/hw/device-assignment.c
From: Avi Kivity a...@redhat.com
This allows Linux to mask cpuid bits if, for example, nx is enabled on only
some cpus.
Signed-off-by: Avi Kivity a...@redhat.com
Signed-off-by: Marcelo Tosatti mtosa...@redhat.com
diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
index 003a0ca..410d2d1 100644
From: Avi Kivity a...@redhat.com
We now use load_gs_index() to load gs safely; unfortunately this also
changes MSR_KERNEL_GS_BASE, which we managed separately. This resulted
in confusion and breakage running 32-bit host userspace on a 64-bit kernel.
Fix by
- saving guest MSR_KERNEL_GS_BASE
From: Jan Kiszka jan.kis...@siemens.com
When we deassign a guest IRQ, clear the potentially asserted guest line.
There might be no chance for the guest to do this, specifically if we
switch from INTx to MSI mode.
Acked-by: Alex Williamson alex.william...@redhat.com
Acked-by: Michael S. Tsirkin
From: Jan Kiszka jan.kis...@siemens.com
Cosmetic change, but it helps to correlate IRQs with PCI devices.
Acked-by: Alex Williamson alex.william...@redhat.com
Acked-by: Michael S. Tsirkin m...@redhat.com
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
Signed-off-by: Marcelo Tosatti
From: Jan Kiszka jan.kis...@siemens.com
The guest may change states that pci_reset_function does not touch. So
we better save/restore the assigned device across guest usage.
Acked-by: Alex Williamson alex.william...@redhat.com
Acked-by: Michael S. Tsirkin m...@redhat.com
Signed-off-by: Jan
From: Jan Kiszka jan.kis...@siemens.com
Adds API documentation for KVM_[DE]ASSIGN_PCI_DEVICE,
KVM_[DE]ASSIGN_DEV_IRQ, KVM_SET_GSI_ROUTING, KVM_ASSIGN_SET_MSIX_NR, and
KVM_ASSIGN_SET_MSIX_ENTRY.
Acked-by: Alex Williamson alex.william...@redhat.com
Acked-by: Michael S. Tsirkin m...@redhat.com
From: Xiao Guangrong xiaoguangr...@cn.fujitsu.com
If reserved bit is set, we need inject the #PF with PFEC.RSVD=1,
but shadow_notrap_nonpresent_pte injects #PF with PFEC.RSVD=0 only
Signed-off-by: Xiao Guangrong xiaoguangr...@cn.fujitsu.com
Signed-off-by: Marcelo Tosatti mtosa...@redhat.com
From: Takuya Yoshikawa yoshikawa.tak...@oss.ntt.co.jp
In kvm_cpu_hotplug(), only CPU_STARTING case is protected by kvm_lock.
This patch adds missing protection for CPU_DYING case.
Signed-off-by: Takuya Yoshikawa yoshikawa.tak...@oss.ntt.co.jp
Signed-off-by: Marcelo Tosatti mtosa...@redhat.com
From: Avi Kivity a...@redhat.com
Signed-off-by: Avi Kivity a...@redhat.com
Signed-off-by: Marcelo Tosatti mtosa...@redhat.com
diff --git a/arch/x86/kvm/emulate.c b/arch/x86/kvm/emulate.c
index 38b6e8d..ffd6e01 100644
--- a/arch/x86/kvm/emulate.c
+++ b/arch/x86/kvm/emulate.c
@@ -20,16 +20,9 @@
From: Takuya Yoshikawa yoshikawa.tak...@oss.ntt.co.jp
The naming convension of hardware_[dis|en]able family is little bit confusing
because only hardware_[dis|en]able_all are using _nolock suffix.
Renaming current hardware_[dis|en]able() to *_nolock() and using
hardware_[dis|en]able() as wrapper
From: Jan Kiszka jan.kis...@siemens.com
This improves the IRQ forwarding for assigned devices: By using the
kernel's threaded IRQ scheme, we can get rid of the latency-prone work
queue and simplify the code in the same run.
Moreover, we no longer have to hold assigned_dev_lock while raising the
From: Avi Kivity a...@redhat.com
Failed emulation is reported via a tracepoint; the cmps printk is pointless.
Signed-off-by: Avi Kivity a...@redhat.com
Signed-off-by: Marcelo Tosatti mtosa...@redhat.com
diff --git a/arch/x86/kvm/emulate.c b/arch/x86/kvm/emulate.c
index ffd6e01..3325b47 100644
From: Avi Kivity a...@redhat.com
Linear addresses are supposed to already have segment checks performed on them;
if we play with these addresses the checks become invalid.
Signed-off-by: Avi Kivity a...@redhat.com
Signed-off-by: Marcelo Tosatti mtosa...@redhat.com
diff --git
From: Avi Kivity a...@redhat.com
Currently the x86 emulator converts the segment register associated with
an operand into a segment base which is added into the operand address.
This loss of information results in us not doing segment limit checks properly.
Replace struct operand's addr.mem
From: Marcelo Tosatti mtosa...@redhat.com
Conflicts:
arch/x86/kvm/svm.c
kernel/sched.c
Signed-off-by: Marcelo Tosatti mtosa...@redhat.com
--
To unsubscribe from this list: send the line unsubscribe kvm-commits in
the body of a message to majord...@vger.kernel.org
More majordomo
From: Avi Kivity a...@redhat.com
cea15c2 (KVM: Move KVM context switch into own function) split vmx_vcpu_run()
to prevent multiple copies of the context switch from being generated (causing
problems due to a label). This patch folds them back together again and adds
the __noclone attribute to
From: Shane Wang shane.w...@intel.com
Inform user to either disable TXT in the BIOS or do TXT launch
with tboot before enabling KVM since some BIOSes do not set
FEATURE_CONTROL_VMXON_ENABLED_OUTSIDE_SMX bit when TXT is enabled.
Signed-off-by: Shane Wang shane.w...@intel.com
Signed-off-by:
From: Avi Kivity a...@redhat.com
The exit reason alone is insufficient to understand exactly why an exit
occured; add ISA-specific trace parameters for additional information.
Because fetching these parameters is expensive on vmx, and because these
parameters are fetched even if tracing is
From: Avi Kivity a...@redhat.com
exit_reason's meaning depend on the instruction set; record it so a trace
taken on one machine can be interpreted on another.
Signed-off-by: Avi Kivity a...@redhat.com
diff --git a/arch/x86/kvm/svm.c b/arch/x86/kvm/svm.c
index c6a7798..b83954e 100644
---
From: Michael S. Tsirkin m...@redhat.com
Store irq routing table pointer in the irqfd object,
and use that to inject MSI directly without bouncing out to
a kernel thread.
While we touch this structure, rearrange irqfd fields to make fastpath
better packed for better cache utilization.
This also
From: Avi Kivity a...@redhat.com
While not required by the spec, some guests (Linux)
rely on nmi being blocked by an IF-enabling sti. Add
a unit test for this condition.
Signed-off-by: Avi Kivity a...@redhat.com
Signed-off-by: Marcelo Tosatti mtosa...@redhat.com
diff --git a/x86/apic.c
From: Avi Kivity a...@redhat.com
This allows the smp support, which uses the boot idt, to work.
Signed-off-by: Avi Kivity a...@redhat.com
Signed-off-by: Marcelo Tosatti mtosa...@redhat.com
diff --git a/x86/apic.c b/x86/apic.c
index 48fa0f7..165f820 100644
--- a/x86/apic.c
+++ b/x86/apic.c
@@
On 11/23/2010 08:41 AM, Avi Kivity wrote:
On 11/23/2010 01:00 AM, Anthony Liguori wrote:
qemu-kvm vcpu threads don't response to SIGSTOP/SIGCONT. Instead of
teaching
them to respond to these signals, introduce monitor commands that stop
and start
individual vcpus.
The purpose of these commands
On Tuesday 23 November 2010 15:54:40 Avi Kivity wrote:
On 11/23/2010 08:35 AM, Yang, Sheng wrote:
On Tuesday 23 November 2010 14:17:28 Avi Kivity wrote:
On 11/23/2010 08:09 AM, Yang, Sheng wrote:
Hi Avi,
I've purposed the following API for mask bit support.
On 11/23/2010 02:11 AM, Daniel Gollub wrote:
On Monday, November 22, 2010 10:37:05 pm Avi Kivity wrote:
On 11/11/2010 11:22 AM, Daniel Gollub wrote:
On Thursday, November 11, 2010 02:31:06 am Avi Kivity wrote:
Daniel, the buildbot has been fairly effective in keeping qemu-kvm.git
On 11/16/2010 05:12 PM, Steven Rostedt wrote:
Hmm, I'll try it out on the latest kernel. Would you be able to upload
the trace.dat that does not work someplace that I can get it. I'd like
to take a look at it. If you don't have a place to put it, I could give
you access to my box, and
Currently the kvm plugin only decodes vmx exit reasons; the first patch
in this series adds support for the svm instruction set.
Second patch fixes a typo.
A couple of fields were added to the kvm_exit tracepoint; the third patch
prints them out.
Avi Kivity (3):
kvm: parse svm exit reason
Signed-off-by: Avi Kivity a...@redhat.com
---
plugin_kvm.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/plugin_kvm.c b/plugin_kvm.c
index c8e8b8c..659b27f 100644
--- a/plugin_kvm.c
+++ b/plugin_kvm.c
@@ -236,7 +236,7 @@ static const char *find_exit_reason(unsigned
svm exit reasons use different code than vmx; use the new isa trace field
to select the instruction set and display the strings accordingly.
Signed-off-by: Avi Kivity a...@redhat.com
---
plugin_kvm.c | 114 ++
1 files changed, 107
Signed-off-by: Avi Kivity a...@redhat.com
---
plugin_kvm.c |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/plugin_kvm.c b/plugin_kvm.c
index 659b27f..c1cb2e4 100644
--- a/plugin_kvm.c
+++ b/plugin_kvm.c
@@ -244,6 +244,7 @@ static int kvm_exit_handler(struct trace_seq
On 11/16/2010 05:13 PM, Steven Rostedt wrote:
BTW, what does /debug/tracing/printk_formats show?
Empty.
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More
On Tue, Nov 23, 2010 at 10:13:43AM +0800, lidong chen wrote:
I test the performance between per-vhost kthread disable and enable.
Test method:
Send the same traffic load between per-vhost kthread disable and
enable, and compare the cpu rate of host os.
I run five vm on kvm, each of them
On Tue, Nov 23, 2010 at 02:09:52PM +0800, Yang, Sheng wrote:
Hi Avi,
I've purposed the following API for mask bit support.
The main point is, QEmu can know which entries are enabled(by
pci_enable_msix()).
Unfortunately, it can't I think, unless all your guests are linux.
enabled entries
On Mon, 22 Nov 2010 17:00:41 -0600
Anthony Liguori anth...@codemonkey.ws wrote:
On 11/22/2010 03:45 PM, Chris Wright wrote:
* Juan Quintela (quint...@redhat.com) wrote:
Please send in any agenda items you are interested in covering.
usb-ccid
- vcpu hard limits
-
The Buildbot has detected a new failure of disable_kvm_x86_64_debian_5_0 on
qemu-kvm.
Full details are available at:
http://buildbot.b1-systems.de/qemu-kvm/builders/disable_kvm_x86_64_debian_5_0/builds/643
Buildbot URL: http://buildbot.b1-systems.de/qemu-kvm/
Buildslave for this Build:
The Buildbot has detected a new failure of disable_kvm_x86_64_out_of_tree on
qemu-kvm.
Full details are available at:
http://buildbot.b1-systems.de/qemu-kvm/builders/disable_kvm_x86_64_out_of_tree/builds/592
Buildbot URL: http://buildbot.b1-systems.de/qemu-kvm/
Buildslave for this Build:
The Buildbot has detected a new failure of disable_kvm_i386_debian_5_0 on
qemu-kvm.
Full details are available at:
http://buildbot.b1-systems.de/qemu-kvm/builders/disable_kvm_i386_debian_5_0/builds/644
Buildbot URL: http://buildbot.b1-systems.de/qemu-kvm/
Buildslave for this Build:
The Buildbot has detected a new failure of default_x86_64_debian_5_0 on
qemu-kvm.
Full details are available at:
http://buildbot.b1-systems.de/qemu-kvm/builders/default_x86_64_debian_5_0/builds/653
Buildbot URL: http://buildbot.b1-systems.de/qemu-kvm/
Buildslave for this Build: b1_qemu_kvm_1
The Buildbot has detected a new failure of default_x86_64_out_of_tree on
qemu-kvm.
Full details are available at:
http://buildbot.b1-systems.de/qemu-kvm/builders/default_x86_64_out_of_tree/builds/594
Buildbot URL: http://buildbot.b1-systems.de/qemu-kvm/
Buildslave for this Build:
The Buildbot has detected a new failure of disable_kvm_i386_out_of_tree on
qemu-kvm.
Full details are available at:
http://buildbot.b1-systems.de/qemu-kvm/builders/disable_kvm_i386_out_of_tree/builds/592
Buildbot URL: http://buildbot.b1-systems.de/qemu-kvm/
Buildslave for this Build:
On 11/23/2010 10:30 AM, Yang, Sheng wrote:
On Tuesday 23 November 2010 15:54:40 Avi Kivity wrote:
On 11/23/2010 08:35 AM, Yang, Sheng wrote:
On Tuesday 23 November 2010 14:17:28 Avi Kivity wrote:
On 11/23/2010 08:09 AM, Yang, Sheng wrote:
Hi Avi,
I've
The Buildbot has detected a new failure of default_i386_debian_5_0 on qemu-kvm.
Full details are available at:
http://buildbot.b1-systems.de/qemu-kvm/builders/default_i386_debian_5_0/builds/655
Buildbot URL: http://buildbot.b1-systems.de/qemu-kvm/
Buildslave for this Build: b1_qemu_kvm_2
The Buildbot has detected a new failure of default_i386_out_of_tree on qemu-kvm.
Full details are available at:
http://buildbot.b1-systems.de/qemu-kvm/builders/default_i386_out_of_tree/builds/592
Buildbot URL: http://buildbot.b1-systems.de/qemu-kvm/
Buildslave for this Build: b1_qemu_kvm_2
23.11.2010 15:08, Luiz Capitulino wrote:
[]
- 0.14 (release date, bug day, -rc planning, etc)
Um, can we have some 0.13.x before, please?.. :)
/mjt
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo info at
On Tue, Nov 23, 2010 at 02:47:33PM +0200, Avi Kivity wrote:
On 11/23/2010 10:30 AM, Yang, Sheng wrote:
On Tuesday 23 November 2010 15:54:40 Avi Kivity wrote:
On 11/23/2010 08:35 AM, Yang, Sheng wrote:
On Tuesday 23 November 2010 14:17:28 Avi Kivity wrote:
On 11/23/2010 08:09 AM,
At this point, I'd suggest testing vhost-net on the upstream kernel,
not on rhel kernels. The change that introduced per-device threads is:
c23f3445e68e1db0e74099f264bc5ff5d55ebdeb
i will try this tomorrow.
Is CONFIG_SCHED_DEBUG set?
yes. CONFIG_SCHED_DEBUG=y.
2010/11/23 Michael S. Tsirkin
As a preparation for providing little-endian bitops for all architectures,
This removes generic_ prefix from little-endian bitops function names
in asm-generic/bitops/le.h.
s/generic_find_next_le_bit/find_next_le_bit/
s/generic_find_next_zero_le_bit/find_next_zero_le_bit/
On Tue, Nov 23, 2010 at 09:23:41PM +0800, lidong chen wrote:
At this point, I'd suggest testing vhost-net on the upstream kernel,
not on rhel kernels. The change that introduced per-device threads is:
c23f3445e68e1db0e74099f264bc5ff5d55ebdeb
i will try this tomorrow.
Is CONFIG_SCHED_DEBUG
No need to include asm-generic/bitops/le.h as all architectures
provide little-endian bit operations now.
Signed-off-by: Akinobu Mita akinobu.m...@gmail.com
Cc: Avi Kivity a...@redhat.com
Cc: Marcelo Tosatti mtosa...@redhat.com
Cc: kvm@vger.kernel.org
---
No change from previous submission
On 11/23/2010 12:41 AM, Avi Kivity wrote:
On 11/23/2010 01:00 AM, Anthony Liguori wrote:
qemu-kvm vcpu threads don't response to SIGSTOP/SIGCONT. Instead of
teaching
them to respond to these signals, introduce monitor commands that
stop and start
individual vcpus.
The purpose of these
On Tuesday 23 November 2010 20:47:33 Avi Kivity wrote:
On 11/23/2010 10:30 AM, Yang, Sheng wrote:
On Tuesday 23 November 2010 15:54:40 Avi Kivity wrote:
On 11/23/2010 08:35 AM, Yang, Sheng wrote:
On Tuesday 23 November 2010 14:17:28 Avi Kivity wrote:
On 11/23/2010 08:09 AM,
On 11/23/2010 02:16 AM, Dor Laor wrote:
On 11/23/2010 08:41 AM, Avi Kivity wrote:
On 11/23/2010 01:00 AM, Anthony Liguori wrote:
qemu-kvm vcpu threads don't response to SIGSTOP/SIGCONT. Instead of
teaching
them to respond to these signals, introduce monitor commands that stop
and start
On 11/23/2010 03:51 PM, Anthony Liguori wrote:
On 11/23/2010 12:41 AM, Avi Kivity wrote:
On 11/23/2010 01:00 AM, Anthony Liguori wrote:
qemu-kvm vcpu threads don't response to SIGSTOP/SIGCONT. Instead of
teaching
them to respond to these signals, introduce monitor commands that
stop and
On Tuesday 23 November 2010 20:04:16 Michael S. Tsirkin wrote:
On Tue, Nov 23, 2010 at 02:09:52PM +0800, Yang, Sheng wrote:
Hi Avi,
I've purposed the following API for mask bit support.
The main point is, QEmu can know which entries are enabled(by
pci_enable_msix()).
On 11/23/2010 03:57 PM, Yang, Sheng wrote:
Yeah, but won't be included in this patchset.
What API changes are needed? I'd like to see the complete API.
I am not sure about it. But I suppose the structure should be the same? In fact
it's pretty hard for me to image what's needed for
On 11/23/2010 08:00 AM, Avi Kivity wrote:
If we could catch SIGSTOP, then it would be easy to unblock it only
while running in guest context. It would then stop on exit to
userspace.
Yeah, that's not a bad idea.
Except we can't.
Yeah, I s:SIGSTOP:SIGUSR1:g.
Using monitor commands is
On Tue, 2010-11-23 at 13:04 +0200, Avi Kivity wrote:
On 11/16/2010 05:13 PM, Steven Rostedt wrote:
BTW, what does /debug/tracing/printk_formats show?
Empty.
So you have real trace_printk's not bprintk's?
That is, if the format is not a const, then we fall back to
On 11/23/2010 04:24 PM, Anthony Liguori wrote:
Using monitor commands is fairly heavyweight for something as high
frequency as this. What control period do you see people using?
Maybe we should define USR1 for vcpu start/stop.
What happens if one vcpu is stopped while another is
Am 22.11.2010 14:55, schrieb Stefan Hajnoczi:
On Mon, Nov 22, 2010 at 1:38 PM, Juan Quintela quint...@redhat.com wrote:
Please send in any agenda items you are interested in covering.
QCOW2 performance roadmap:
* What can be done to achieve near-raw image format performance?
* Benchmark
On 11/23/2010 04:30 PM, Steven Rostedt wrote:
On Tue, 2010-11-23 at 13:04 +0200, Avi Kivity wrote:
On 11/16/2010 05:13 PM, Steven Rostedt wrote:
BTW, what does /debug/tracing/printk_formats show?
Empty.
So you have real trace_printk's not bprintk's?
What are bprintk()s?
That
On Tue, Nov 23, 2010 at 2:37 PM, Kevin Wolf kw...@redhat.com wrote:
Am 22.11.2010 14:55, schrieb Stefan Hajnoczi:
On Mon, Nov 22, 2010 at 1:38 PM, Juan Quintela quint...@redhat.com wrote:
Please send in any agenda items you are interested in covering.
QCOW2 performance roadmap:
* What can
kvm_setup_cpuid seems unused, so remove it.
Signed-off-by: Michael S. Tsirkin m...@redhat.com
diff --git a/kvm/libkvm/libkvm-x86.c b/kvm/libkvm/libkvm-x86.c
index f1aef76..2b12408 100644
--- a/kvm/libkvm/libkvm-x86.c
+++ b/kvm/libkvm/libkvm-x86.c
@@ -466,45 +466,6 @@ __u64
On Tue, Nov 23, 2010 at 04:06:20PM +0200, Avi Kivity wrote:
So instead of
- guest reads/writes msix
- kvm filters mmio, implements some, passes others to userspace
we have
- guest reads/writes msix
- kvm implements all
- some writes generate an additional notification
On Tue, Nov 23, 2010 at 05:11:19PM +0200, Michael S. Tsirkin wrote:
On Tue, Nov 23, 2010 at 04:06:20PM +0200, Avi Kivity wrote:
So instead of
- guest reads/writes msix
- kvm filters mmio, implements some, passes others to userspace
we have
- guest reads/writes msix
Anthony, Blue
No comments on this patch series for almost a week. Can it be applied?
On Wed, Nov 17, 2010 at 06:43:47PM +0200, Gleb Natapov wrote:
I am using open firmware naming scheme to specify device path names.
In this version: added SCSI bus support. Pass boot order list as file
to
http://www.cir-rosario.com.ar/peper.php
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Tue, 2010-11-23 at 16:37 +0200, Avi Kivity wrote:
On 11/23/2010 04:30 PM, Steven Rostedt wrote:
On Tue, 2010-11-23 at 13:04 +0200, Avi Kivity wrote:
On 11/16/2010 05:13 PM, Steven Rostedt wrote:
BTW, what does /debug/tracing/printk_formats show?
Empty.
So you
On 11/23/2010 5:41 AM, Michael S. Tsirkin wrote:
On Tue, Nov 23, 2010 at 09:23:41PM +0800, lidong chen wrote:
At this point, I'd suggest testing vhost-net on the upstream kernel,
not on rhel kernels. The change that introduced per-device threads is:
c23f3445e68e1db0e74099f264bc5ff5d55ebdeb
i
qcow2 performance roadmap
- What can be done to achieve near-raw image format performance?
- some discussion points from Kevin on list
http://lists.nongnu.org/archive/html/qemu-devel/2010-11/msg02126.html
- please follow up on the list
- some perf numbers (latest upstream qcow2 compared
On Tue, Nov 23, 2010 at 05:24:44PM +0200, Gleb Natapov wrote:
On Tue, Nov 23, 2010 at 05:11:19PM +0200, Michael S. Tsirkin wrote:
On Tue, Nov 23, 2010 at 04:06:20PM +0200, Avi Kivity wrote:
So instead of
- guest reads/writes msix
- kvm filters mmio, implements some,
On 11/23/2010 09:31 AM, Gleb Natapov wrote:
Anthony, Blue
No comments on this patch series for almost a week. Can it be applied?
Does that mean everyone's happy or have folks not gotten around to
review it?
IOW, last call if you have objections :-)
Regards,
Anthony Liguori
On Wed,
qemu-kvm vcpu threads don't response to SIGSTOP/SIGCONT. Instead of teaching
them to respond to these signals (which cannot be trapped), use SIGUSR1 to
approximate the behavior of SIGSTOP/SIGCONT.
The purpose of this is to implement CPU hard limits using an external tool that
watches the CPU
On Tue, 2010-11-23 at 12:58 +0200, Avi Kivity wrote:
Currently the kvm plugin only decodes vmx exit reasons; the first patch
in this series adds support for the svm instruction set.
Second patch fixes a typo.
A couple of fields were added to the kvm_exit tracepoint; the third patch
prints
On Tue, Nov 23, 2010 at 4:12 PM, Anthony Liguori
aligu...@linux.vnet.ibm.com wrote:
On 11/23/2010 09:31 AM, Gleb Natapov wrote:
Anthony, Blue
No comments on this patch series for almost a week. Can it be applied?
Does that mean everyone's happy or have folks not gotten around to review
On Tue, Nov 23, 2010 at 4:49 PM, Anthony Liguori aligu...@us.ibm.com wrote:
qemu-kvm vcpu threads don't response to SIGSTOP/SIGCONT. Instead of teaching
them to respond to these signals (which cannot be trapped), use SIGUSR1 to
approximate the behavior of SIGSTOP/SIGCONT.
The purpose of this
On 11/23/2010 01:35 PM, Blue Swirl wrote:
On Tue, Nov 23, 2010 at 4:49 PM, Anthony Liguorialigu...@us.ibm.com wrote:
qemu-kvm vcpu threads don't response to SIGSTOP/SIGCONT. Instead of teaching
them to respond to these signals (which cannot be trapped), use SIGUSR1 to
approximate the
On 11/23/2010 10:46 PM, Anthony Liguori wrote:
+static __thread int sigusr1_wfd;
While OpenBSD finally updated the default compiler to 4.2.1 from 3.x
series, thread local storage is still not supported:
Hrm, is there a portable way to do this (distinguish a signal on a
particular thread)?
On 11/23/2010 05:43 PM, Paolo Bonzini wrote:
On 11/23/2010 10:46 PM, Anthony Liguori wrote:
+static __thread int sigusr1_wfd;
While OpenBSD finally updated the default compiler to 4.2.1 from 3.x
series, thread local storage is still not supported:
Hrm, is there a portable way to do this
Hi Gleb,
On Tue, Nov 23, 2010 at 05:31:41PM +0200, Gleb Natapov wrote:
Anthony, Blue
No comments on this patch series for almost a week. Can it be applied?
My apologies - I haven't had time to review.
On Wed, Nov 17, 2010 at 06:43:47PM +0200, Gleb Natapov wrote:
I am using open firmware
On Tuesday 23 November 2010 22:06:20 Avi Kivity wrote:
On 11/23/2010 03:57 PM, Yang, Sheng wrote:
Yeah, but won't be included in this patchset.
What API changes are needed? I'd like to see the complete API.
I am not sure about it. But I suppose the structure should be the
On 11/24/2010 02:15 AM, Anthony Liguori wrote:
Is it signal safe?
Yes, at heart it is just a somewhat more expensive access to
pthread_self()-some_array[key].
BTW, this is all only theoretical. This is in the KVM io thread code
which is already highly unportable.
True, and newer
84 matches
Mail list logo
