On Tue, Jul 22, 2014 at 6:13 PM, David Rientjes wrote:
> On Tue, 22 Jul 2014, Nick Krause wrote:
>
>> >> This patch removes a fix me by including linux/types.h in kvm_para.h
>> >> as stated by the fix me in main.c and also removes the comment from
>> >
H
>>
>> #include
>> -
>> -
>> +#include
>> static inline int kvm_para_has_feature(unsigned int feature)
>> {
>> if (kvm_arch_para_features() & (1UL << feature))
>
> There's no build error reported that would indicate t
backwards time was visible in the guest.
>
> I've managed to get my hands on a broken migration stream from Nick.
> There I looked at the curr_clocksource structure and saw that the last
> seen time on the kvmclock clock source was greater than the value that
> the kvmclo
gin, or even if it's possible at all. Are these CPUs just too old, or
is a fixup missing in qemu (or kvm)?
/Nick
--
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 28/02/14 12:57, Paolo Bonzini wrote:
> Il 28/02/2014 13:16, Nick Thomas ha scritto:
>> I'd love to get this working, but I'm a little ignorant on where to
>> begin, or even if it's possible at all. Are these CPUs just too old, or
>> is a fixup missing in qem
Every time a try and start a kvm-based VM with virt-manager the guest
crashes during boot-up with this message in the host's kernel logger.
[ 6762.680687] device eth0 entered promiscuous mode
[ 6769.287090] kvm: 14513: cpu0 unhandled rdmsr: 0xc001100d
[ 6769.287151] kvm: 14513: cpu0 unhandled rdm
On Tue, Jan 24, 2012 at 6:24 AM, Ademar de Souza Reis Jr.
wrote:
> On Mon, Jan 23, 2012 at 04:54:04PM -0800, Nick H wrote:
>> Hello All,
>>
>> Non-development question, apologies if I am posting to the wrong list,
>> but I cannot seem to find linux kvm forum 2010 vide
Hello All,
Non-development question, apologies if I am posting to the wrong list,
but I cannot seem to find linux kvm forum 2010 videos at the following
link:
http://www.linux-kvm.org/page/KVM_Forum_2010
Is there some place else where they might be present ?
Nick
--
To unsubscribe from this
gpa->hpa lookup inside them. In case of EPT what does each
level/each entry of shadow page table hold ?
Thanks in advance,
Nick
> On Tue, Jan 10, 2012 at 11:41:41AM -0800, Nick H wrote:
>> Hello All,
>>
>> I am preparing for a presentation for my community college, new
d of you.
Thanks in advance and apologies if I am sending this to the wrong
list. Any help appreciated...hopefully questions are not too vague..
Nick
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More major
kernel-hackers) to profile CentOS 5
systems, in order to pinpoint IO bottlenecks, or other scheduling problems?
We don't currently have the option of upgrading to CentOS 6, and would prefer to
use stock kernels in production. This may mean some of the currently-used tools
can't be a
ought that using the wrong clock would not actually *cause*
hangs like this. Or is that what you're implying?
Thanks
Nick
--
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
de
> >
> > @@ -274,6 +275,7 @@ int __get_user_pages_fast(unsigned long start, int
> > nr_pages, int write,
> >
> > return nr;
> > }
> > +EXPORT_SYMBOL_GPL(__get_user_pages_fast);
> >
> > /**
> > * get_user_pages_fast() - pin user page
On Sun, Jun 27, 2010 at 12:17:42PM +0300, Avi Kivity wrote:
> On 06/24/2010 06:14 PM, Nick Piggin wrote:
> >On Thu, Jun 24, 2010 at 12:19:32PM +0300, Avi Kivity wrote:
> >>I see really slow vmalloc performance on 2.6.35-rc3:
> >Can you try this patch?
> >http://
| --100.00%--
> 0x1dfc4a8878e71362
>
>
> It seems completely wrong - iterating 8 levels of a binary tree
> shouldn't take half a millisecond.
It's not iterating down the tree, it's iterating through the
nodes to find a free area. Slows down becaus
On Wed, Jun 16, 2010 at 10:39:41AM +0200, Ingo Molnar wrote:
>
> (Cc:-ed various performance/optimization folks)
>
> * Avi Kivity wrote:
>
> > On 06/16/2010 10:32 AM, H. Peter Anvin wrote:
> > >On 06/16/2010 12:24 AM, Avi Kivity wrote:
> > >>Ingo, Peter, any feedback on this?
> > > Conceptually
On Thu, Jun 03, 2010 at 05:17:30PM +0200, Andi Kleen wrote:
> On Thu, Jun 03, 2010 at 10:38:32PM +1000, Nick Piggin wrote:
> > And they aren't even using ticket spinlocks!!
>
> I suppose they simply don't have unfair memory. Makes things easier.
That would certainly
On Thu, Jun 03, 2010 at 06:28:21PM +0530, Srivatsa Vaddagiri wrote:
> On Thu, Jun 03, 2010 at 10:38:32PM +1000, Nick Piggin wrote:
> > Holding a ticket in the queue is effectively the same as holding the
> > lock, from the pov of processes waiting behind.
> >
> > The d
On Thu, Jun 03, 2010 at 05:34:50PM +0530, Srivatsa Vaddagiri wrote:
> On Thu, Jun 03, 2010 at 08:38:55PM +1000, Nick Piggin wrote:
> > > Guest side:
> > >
> > > static inline void spin_lock(spinlock_t *lock)
> > > {
> > > raw_spin_lock(&l
On Thu, Jun 03, 2010 at 09:50:51AM +0530, Srivatsa Vaddagiri wrote:
> On Wed, Jun 02, 2010 at 12:00:27PM +0300, Avi Kivity wrote:
> >
> > There are two separate problems: the more general problem is that
> > the hypervisor can put a vcpu to sleep while holding a lock, causing
> > other vcpus to sp
On Thu, Jun 03, 2010 at 10:52:51AM +0200, Andi Kleen wrote:
> On Thu, Jun 03, 2010 at 09:50:51AM +0530, Srivatsa Vaddagiri wrote:
> > On Wed, Jun 02, 2010 at 12:00:27PM +0300, Avi Kivity wrote:
> > >
> > > There are two separate problems: the more general problem is that
> > > the hypervisor can p
o
> naturally aligned addresses in write-back cacheable memory.)
>
> Oh, that's interesting. Way back when I guess we knew writes were in
> order and it wasn't explicit that reads were, hence smp_rmb() using a
> locked atomic.
>
> Here is a post by Nick Piggin from 200
ngelog. A discussion of
> > where the memory savings comes from, and how far does things like
> > sharing of fs image, or ballooning goes and how much extra savings we
> > get from this... with people from other hypervisors involved as well.
> > Have I missed this kind of disc
that doesn't mean much. We should rub
> bottles with words like "hugh" and "nick" on them to be sure.
I haven't looked too closely at it yet sorry. Hugh has a great eye for
these details, though, hint hint :)
As everyone knows, my favourite thing is to say nasty thin
On Sunday 05 April 2009 01:35:18 Izik Eidus wrote:
> This driver is very useful for KVM as in cases of runing multiple guests
> operation system of the same type.
> (For desktop work loads we have achived more than x2 memory overcommit
> (more like x3))
Interesting that it is a desirable workload
On Wednesday 31 December 2008 02:32:50 Avi Kivity wrote:
> Marcelo Tosatti wrote:
> > On Tue, Dec 30, 2008 at 02:53:36PM +1100, Nick Piggin wrote:
> >>> RSP
> >>> ---[ end trace 31811279a2e983e8 ]---
> >>> note: qemu-system-x86[4440] exited w
8d 58 c0 <48> 8b 43 40
> 0f 18 08 48 8d 43 40 4c 39 e0 75 e0 48 c7 c7 c0 d1 RIP
> [] __purge_vmap_area_lazy+0x12c/0x163
> RSP
> ---[ end trace 31811279a2e983e8 ]---
> note: qemu-system-x86[4440] exited with preempt_count 2
>
>
> (gdb) l *(__purge_vmap_
On Thursday 13 November 2008 13:31, Andrea Arcangeli wrote:
> On Thu, Nov 13, 2008 at 03:00:59AM +0100, Andrea Arcangeli wrote:
> > CPU0 migrate.c CPU1 filemap.c
> > --- --
> > find_get_page
> >
On Saturday 08 November 2008 13:13, Glauber Costa wrote:
> On Sat, Nov 08, 2008 at 01:58:32AM +0100, Nick Piggin wrote:
> > On Fri, Nov 07, 2008 at 08:35:50PM -0200, Glauber Costa wrote:
> > > Nick,
> > >
> > > This is the whole set of patches I was talking abo
On Fri, Nov 07, 2008 at 08:35:50PM -0200, Glauber Costa wrote:
> Nick,
>
> This is the whole set of patches I was talking about.
> Patch 3 is the one that in fact fixes the problem
> Patches 1 and 2 are debugging aids I made use of, and could be possibly
> useful to others
>
Excellent, thank you! Good catch
If you agree my previous patch was also good in combination with this one,
then I'll send them all to be merged.
Thanks,
Nick
On Thu, Nov 06, 2008 at 06:58:26PM -0200, Glauber Costa wrote:
> Current vmalloc restart search for a free area in case we
>
On Thu, Oct 30, 2008 at 09:28:54AM -0200, Glauber Costa wrote:
> On Thu, Oct 30, 2008 at 05:49:41AM +0100, Nick Piggin wrote:
> > On Wed, Oct 29, 2008 at 08:07:37PM -0200, Glauber Costa wrote:
> > > On Wed, Oct 29, 2008 at 11:43:33AM +0100, Nick Piggin wrote:
> > > >
On Thu, Oct 30, 2008 at 04:04:43PM -0200, Glauber Costa wrote:
> On Thu, Oct 30, 2008 at 11:46:02AM -0500, Matt Mackall wrote:
> > On Thu, 2008-10-30 at 05:49 +0100, Nick Piggin wrote:
> > > I still think we should get rid of the guard pages in non-debug kernels
> > > co
On Wed, Oct 29, 2008 at 08:07:37PM -0200, Glauber Costa wrote:
> On Wed, Oct 29, 2008 at 11:43:33AM +0100, Nick Piggin wrote:
> > On Wed, Oct 29, 2008 at 12:29:40PM +0200, Avi Kivity wrote:
> > > Nick Piggin wrote:
> > > >Hmm, spanning <30MB of memory... h
On Wed, Oct 29, 2008 at 08:07:37PM -0200, Glauber Costa wrote:
> On Wed, Oct 29, 2008 at 11:43:33AM +0100, Nick Piggin wrote:
> > On Wed, Oct 29, 2008 at 12:29:40PM +0200, Avi Kivity wrote:
> > > Nick Piggin wrote:
> > > >Hmm, spanning <30MB of memory... h
On Wed, Oct 29, 2008 at 12:29:40PM +0200, Avi Kivity wrote:
> Nick Piggin wrote:
> >Hmm, spanning <30MB of memory... how much vmalloc space do you have?
> >
> >
>
> From the original report:
>
> >VmallocTotal: 122880 kB
> >VmallocUsed: 15
On Wed, Oct 29, 2008 at 07:48:56AM -0200, Glauber Costa wrote:
> 0xf7bfe000-0xf7c08192 hpet_enable+0x2d/0x279 phys=fed0 ioremap
> 0xf7c02000-0xf7c040008192 acpi_os_map_memory+0x11/0x1a phys=7fed1000
> ioremap
> 0xf7c06000-0xf7c080008192 acpi_os_map_memory+0x11/0x1a phys=7fef20
On Tue, Oct 28, 2008 at 08:55:13PM -0200, Glauber Costa wrote:
> Commit db64fe02258f1507e13fe5212a989922323685ce broke
> KVM (the symptom) for me. The cause is that vmalloc
> allocations fail, despite of the fact that /proc/meminfo
> shows plenty of vmalloc space available.
>
> After some investig
38 matches
Mail list logo
