On Fri, Nov 07, 2014 at 03:58:17PM -0800, Andy Lutomirski wrote:
The int_ret_from_sys_call and syscall tracing code disagrees with
the sysret path as to the value of RCX.
The Intel SDM, the AMD APM, and my laptop all agree that sysret
returns with RCX == RIP. The syscall tracing code does
Hi Razya,
Thanks for the update.
So that's reasonable I think, and I think it makes sense
to keep working on this in isolation - it's more
manageable at this size.
The big questions in my mind:
- What happens if system is lightly loaded?
E.g. a ping/pong benchmark. How much extra CPU are
we
Nerijus Baliunas nerijus at users.sourceforge.net writes:
Paolo Bonzini pbonzini at redhat.com writes:
In the case of Windows it's probably some timing loop that is executed
at startup, and the result depends on frequency scaling in the host.
Try adding this to the XML in the meanwhile,
I have a base Linux From Scratch installation in Virtualbox and I need
virtio-net in the kernel so I can use the virtio-net adapter through
Virtualbox.
I enabled the options listed here: www.linux-kvm.org/page/Virtio but
the network interface does not show up.
I was wondering if there are more
On Mon, Jan 05, 2015 at 10:56:07AM -0800, Andy Lutomirski wrote:
On Mon, Jan 5, 2015 at 7:25 AM, Marcelo Tosatti mtosa...@redhat.com wrote:
On Mon, Dec 22, 2014 at 04:39:57PM -0800, Andy Lutomirski wrote:
The pvclock vdso code was too abstracted to understand easily and
excessively
On Mon, Jan 5, 2015 at 11:17 AM, Marcelo Tosatti mtosa...@redhat.com wrote:
On Mon, Jan 05, 2015 at 10:56:07AM -0800, Andy Lutomirski wrote:
On Mon, Jan 5, 2015 at 7:25 AM, Marcelo Tosatti mtosa...@redhat.com wrote:
On Mon, Dec 22, 2014 at 04:39:57PM -0800, Andy Lutomirski wrote:
The pvclock
On Mon, Jan 5, 2015 at 2:48 PM, Marcelo Tosatti mtosa...@redhat.com wrote:
On Mon, Jan 05, 2015 at 02:38:46PM -0800, Andy Lutomirski wrote:
On Mon, Jan 5, 2015 at 11:17 AM, Marcelo Tosatti mtosa...@redhat.com wrote:
On Mon, Jan 05, 2015 at 10:56:07AM -0800, Andy Lutomirski wrote:
On Mon, Jan
ACCESS BANK PLC ATM DEPARTMENT accessb575 at accountant.com writes:
THIS ACCESS BANK PLC WANT TO INFORM YOU THAT YOUR ATM CARD IS READY,
THAT IF YOU NEED IT, YOU MUST PAY THE $98. IF
YOU ARE READY, MAKE SURE YOU SEND ME YOUR FULL NAMES AND YOUR DIRECT
TELEPHONE NUMBER FOR ME TO CALL YOU SO
On 05/01/2015 19:56, Andy Lutomirski wrote:
1) State: all pvtis marked as PVCLOCK_TSC_STABLE_BIT.
1) Update request for all vcpus, for a TSC_STABLE_BIT - ~TSC_STABLE_BIT
transition.
2) vCPU-1 updates its pvti with new values.
3) vCPU-0 still has not updated its pvti with new values.
On Mon, Jan 05, 2015 at 02:38:46PM -0800, Andy Lutomirski wrote:
On Mon, Jan 5, 2015 at 11:17 AM, Marcelo Tosatti mtosa...@redhat.com wrote:
On Mon, Jan 05, 2015 at 10:56:07AM -0800, Andy Lutomirski wrote:
On Mon, Jan 5, 2015 at 7:25 AM, Marcelo Tosatti mtosa...@redhat.com
wrote:
On
Ping...
Hi Joerg David,
Could you please have a look at the IOMMU part of this series (patch 02 - 04,
patch 06 - 09 , patch 26)?
Hi Thomas, Ingo, Peter,
Could you please have a look at this series, especially for patch 01, 05, 21?
Thanks,
Feng
-Original Message-
From: Wu, Feng
2014-12-23 15:58-0500, Marcelo Tosatti:
For the hrtimer which emulates the tscdeadline timer in the guest,
add an option to advance expiration, and busy spin on VM-entry waiting
for the actual expiration time to elapse.
This allows achieving low latencies in cyclictest (or any scenario
On Mon, Jan 5, 2015 at 4:59 AM, Borislav Petkov b...@alien8.de wrote:
On Fri, Nov 07, 2014 at 03:58:17PM -0800, Andy Lutomirski wrote:
The int_ret_from_sys_call and syscall tracing code disagrees with
the sysret path as to the value of RCX.
The Intel SDM, the AMD APM, and my laptop all agree
2015-01-05 19:12+0100, Radim Krcmar:
(Right now, __delay() = delay_tsc()
whenever the hardware has TSC, regardless of stability, thus always.)
(For quantifiers' sake, there also is 'tsc_disabled' variable.)
--
To unsubscribe from this list: send the line
On Mon, Jan 5, 2015 at 7:25 AM, Marcelo Tosatti mtosa...@redhat.com wrote:
On Mon, Dec 22, 2014 at 04:39:57PM -0800, Andy Lutomirski wrote:
The pvclock vdso code was too abstracted to understand easily and
excessively paranoid. Simplify it for a huge speedup.
This opens the door for
On Mon, Dec 22, 2014 at 04:39:57PM -0800, Andy Lutomirski wrote:
The pvclock vdso code was too abstracted to understand easily and
excessively paranoid. Simplify it for a huge speedup.
This opens the door for additional simplifications, as the vdso no
longer accesses the pvti for any vcpu
16 matches
Mail list logo
