On Fri, Feb 17, 2012 at 03:01:07PM +0100, David Cure wrote:
Le Fri, Feb 17, 2012 at 12:07:14PM +0200, Gleb Natapov ecrivait :
Can you do the trace again with -no-hpet on the command line?
Is there a way to only trace events on specific VM ?
-P pid
ok. I take a trace
On Fri, Feb 17, 2012 at 02:25:56PM +0100, Gerd Hoffmann wrote:
Hi,
+/* If we don't specify the name, the bus will be addressed as id.0,
where
+ * id is the parent id. But it seems more natural to address the bus
using
+ * the parent device name. */
+if
On 2/18/12 6:25 AM, Stefan Hajnoczi wrote:
In my case, it is drbd+RAID10, but the bug still applies. It isn't
whenever checkarray runs, but whenever checkarray decides to do a resync,
it will block all IO somewhere before the end of the resync. Then yes, it
isn't long before the guests start
On Sat Feb 18, 2012, Thomas Fjellstrom wrote:
On Sat Feb 18, 2012, Jan Kiszka wrote:
On 2012-02-18 09:50, Thomas Fjellstrom wrote:
On Sat Feb 18, 2012, Jan Kiszka wrote:
On 2012-02-18 05:49, Thomas Fjellstrom wrote:
I just updated my kvm host, kernel upgraded from 2.6.38 up to 3.2,
On Sun, Feb 19, 2012 at 04:57:07PM +0200, Michael S. Tsirkin wrote:
On Fri, Feb 17, 2012 at 02:25:56PM +0100, Gerd Hoffmann wrote:
Hi,
+/* If we don't specify the name, the bus will be addressed as
id.0, where
+ * id is the parent id. But it seems more natural to address
Changes in v2:
Add UIP check logic.
Add logic that next second tick will occur in exactly 500ms later after setting
the clock
Current RTC emulation uses periodic timer(2 timers per second) to update RTC
clock. And it will stop CPU staying at deep C-state for long period. Our
experience shows
There has no need to use two periodic timer to update RTC time.
In this patch, we only update it when guest reading it.
Signed-off-by: Yang Zhang yang.z.zh...@intel.com
---
hw/mc146818rtc.c | 199 +++---
1 files changed, 56 insertions(+), 143
Use timer to emulate alarm. The timer is enabled when AIE is setting
Signed-off-by: Yang Zhang yang.z.zh...@intel.com
---
hw/mc146818rtc.c | 187 ++
1 files changed, 187 insertions(+), 0 deletions(-)
diff --git a/hw/mc146818rtc.c
Use timer to emulate RTC update-ended interrupt. The timer is enabled
only when UIE is setting.
Signed-off-by: Yang Zhang yang.z.zh...@intel.com
---
hw/mc146818rtc.c | 53 -
1 files changed, 48 insertions(+), 5 deletions(-)
diff --git
The UIP(update in progress) is set when RTC is updating. We only
consider the normal oscillator(32Khz) mode.
When time base is 32kHz, the update cycle takes 1984us at the end
of every second. And the update cycle begins 244us later after UIP
is set. So the UIP is set in 2228us at end of every
When a host stops or suspends a VM it will set a flag to show this. The
watchdog will use these functions to determine if a softlockup is real, or the
result of a suspended VM.
Signed-off-by: Eric B Munson emun...@mgebm.net
asm-generic changes Acked-by: Arnd Bergmann a...@arndb.de
Cc:
Changes from V14:
Update documentation for the pvclock api
Changes from V13:
Expand on KVM_KVMCLOCK_CTRL ioctl documentation
Changes from V12:
Re-add missing kvm.c code after rebase
Rename CAP to KVM_CAP_KVMCLOCK_CTRL
Rename ioctl to KVM_KVMCLOCK_CTRL
Changes from V11:
Re-add asm-generic stub
This flag will be used to check if the vm was stopped by the host when a soft
lockup was detected. The host will set the flag when it stops the guest. On
resume, the guest will check this flag if a soft lockup is detected and skip
issuing the warning.
Signed-off-by: Eric B Munson
A suspended VM can cause spurious soft lockup warnings. To avoid these, the
watchdog now checks if the kernel knows it was stopped by the host and skips
the warning if so. When the watchdog is reset successfully, clear the guest
paused flag.
Signed-off-by: Eric B Munson emun...@mgebm.net
Cc:
Now that we have a flag that will tell the guest it was suspended, create an
interface for that communication using a KVM ioctl.
Signed-off-by: Eric B Munson emun...@mgebm.net
Cc: mi...@redhat.com
Cc: h...@zytor.com
Cc: ry...@linux.vnet.ibm.com
Cc: aligu...@us.ibm.com
Cc: mtosa...@redhat.com
Cc:
For IvyBridge Mobile platform, a system hang may occur if a FLR(Function Level
Reset) is asserted to internal graphics.
This quirk patch is workaround for the IVB FLR errata issue.
Signed-off-by: Xudong Hao xudong@intel.com
Signed-off-by: Kay, Allen M allen.m@intel.com
---
On 02/20/2012 01:25 AM, Zhang, Yang Z wrote:
Use timer to emulate RTC update-ended interrupt. The timer is enabled
only when UIE is setting.
The timer needs to be enabled when UF is clear, not when UIE is set. If
UIE is set but the update interrupt is masked you do not need to do
anything; on
On 02/20/2012 01:25 AM, Zhang, Yang Z wrote:
When time base is 32kHz, the update cycle takes 1984us at the end
of every second. And the update cycle begins 244us later after UIP
is set. So the UIP is set in 2228us at end of every second.
I think we can keep UIP set only for 244us, since our
On 02/20/2012 01:24 AM, Zhang, Yang Z wrote:
Changes in v2:
Add UIP check logic.
Add logic that next second tick will occur in exactly 500ms later after
setting the clock
Current RTC emulation uses periodic timer(2 timers per second) to update RTC
clock. And it will stop CPU staying at
The PAPR API allows three sorts of per-virtual-processor areas to be
registered (VPA, SLB shadow buffer, and dispatch trace log), and
furthermore, these can be registered and unregistered for another
virtual CPU. Currently we just update the vcpu fields pointing to
these areas at the time of
20 matches
Mail list logo
