Hollis Blanchard wrote:
> On Sat, 2008-02-16 at 17:09 -0500, Marcelo Tosatti wrote:
>
>> plain text document attachment (kvm-multicall)
>> Batch pte updates and tlb flushes in lazy MMU mode.
>>
>> Signed-off-by: Marcelo Tosatti <[EMAIL PROTECTED]>
>> Cc: Anthony Liguori <[EMAIL PROTECTED]>
>>
>>
Am Montag, 18. Februar 2008 schrieb Avi Kivity:
> > AFAICS there is no guarantee about page-alignment here...
> Kernel data is physically contiguous (true for per-cpu data as well?),
> so no there's issue here.
Modules are loaded into vmalloc space, no? I think, if kvm is built as
module, stati
Bugs item #1895893, was opened at 2008-02-18 10:44
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1895893&group_id=180599
Please note that this message will contain a full copy
Christian Borntraeger wrote:
> Am Montag, 18. Februar 2008 schrieb Avi Kivity:
>
>>> AFAICS there is no guarantee about page-alignment here...
>>>
>
>
>> Kernel data is physically contiguous (true for per-cpu data as well?),
>> so no there's issue here.
>>
>
> Modules are loaded
On Sat, 16 Feb 2008 14:34:09 +0100
Alexander Graf <[EMAIL PROTECTED]> wrote:
> > Whenever the register state becomes consistent with VT again.
> > vmx_set_segment() looks like the right point for turning it off.
>
> Sounds good. As basically the only problem we have are the sanity
> checks d
On Feb 18, 2008, at 10:34 AM, Alexander Graf wrote:
>
> On Feb 18, 2008, at 10:17 AM, Guillaume Thouvenin wrote:
>
>> On Sat, 16 Feb 2008 14:34:09 +0100
>> Alexander Graf <[EMAIL PROTECTED]> wrote:
>>
Whenever the register state becomes consistent with VT again.
vmx_set_segment() looks
On Feb 18, 2008, at 10:17 AM, Guillaume Thouvenin wrote:
> On Sat, 16 Feb 2008 14:34:09 +0100
> Alexander Graf <[EMAIL PROTECTED]> wrote:
>
>>> Whenever the register state becomes consistent with VT again.
>>> vmx_set_segment() looks like the right point for turning it off.
>>
>> Sounds good. As
Zhao, Yunfeng wrote:
>
> Today’s IA32e KVM build fails, here is the error message:
>
> libqemu.a(kvm-tpr-opt.o): In function `enable_vapic':
>
> /workspace/ia32e/nightly/kvm-master-2.6.22-rc4-20080218000132559/kvm-userspace/qemu/kvm-tpr-opt.c:232:
>
> undefined reference to `kvm_enable_vapic'
>
>
Alexander Graf <[EMAIL PROTECTED]> writes:
>
> As everything except gfxboot works, we can simply change gfxboot in
> runtime to use a different value. Unfortunately the mov instruction,
> used to read the SS register is only 2 bytes long, so there is no way to
> binary patch the mov to something th
On Feb 18, 2008, at 12:46 PM, Andi Kleen wrote:
> Alexander Graf <[EMAIL PROTECTED]> writes:
>>
>> As everything except gfxboot works, we can simply change gfxboot in
>> runtime to use a different value. Unfortunately the mov instruction,
>> used to read the SS register is only 2 bytes long, so t
On Sat, Feb 16, 2008 at 03:08:17AM -0800, Andrew Morton wrote:
> On Sat, 16 Feb 2008 11:48:27 +0100 Andrea Arcangeli <[EMAIL PROTECTED]> wrote:
>
> > +void kvm_mmu_notifier_invalidate_range_end(struct mmu_notifier *mn,
> > + struct mm_struct *mm,
> > +
On Sat, Feb 16, 2008 at 05:51:38AM -0600, Robin Holt wrote:
> I am doing this in xpmem with a stack-based structure in the function
> calling get_user_pages. That structure describes the start and
> end address of the range we are doing the get_user_pages on. If an
> invalidate_range_begin comes
I am using TIP.
I found that if try to compile twice, the first time has no problem but
the second time (make clean&&./configure&&make) will meet the error.
>>
>
>I can't reproduce this with the last snapshot. What commits hashes are
>you using?
>
>--
>Do not meddle in the internals of kernels, f
Hey,
I'm still trying to get kvm/qemu to run at 1920x1200x32 widescreen mode
(my tft's resolution). Host is 32bit Gentoo, guest is 32bit Windows XP.
I'm using kvm-60.
Following this post [1], I added the following lines to
kvm-60/vgabios/vbetables-gen.c
{ 1920, 1200, 8 , 0x
hi there
i've read http://kvm.qumranet.com/kvmwiki/Virtio?highlight=%28virtio%29
about virtio. To test it, i got a new 2.6.25-rc2 kernel and kvm-60
(both on debian).
has anybody out there a minimalistic .config to build a minimal guest
kernel image with virtio enabled?
all my tries with virt
Thomas Mueller wrote:
> hi there
>
> i've read http://kvm.qumranet.com/kvmwiki/Virtio?highlight=%28virtio%29
> about virtio. To test it, i got a new 2.6.25-rc2 kernel and kvm-60
> (both on debian).
>
> has anybody out there a minimalistic .config to build a minimal guest
> kernel image with vir
Zhao, Yunfeng wrote:
> I am using TIP.
> I found that if try to compile twice, the first time has no problem but
> the second time (make clean&&./configure&&make) will meet the error.
>
>
Yes, 'make clean' was too eager. Fixed.
--
error compiling committee.c: too many arguments to function
Bugs item #1896213, was opened at 2008-02-18 17:42
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1896213&group_id=180599
Please note that this message will contain a full copy
Hi Anthony
>> has anybody out there a minimalistic .config to build a minimal guest
>> kernel image with virtio enabled?
>>
>
> I usually do a make defconfig, enable the CONFIG_VIRTIO_* options in
> .config, then do a make oldconfig and answer 'y' to all of the questions.
ok, i'll give it a
Bugs item #1896261, was opened at 2008-02-18 18:54
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1896261&group_id=180599
Please note that this message will contain a full copy
Thomas Mueller wrote:
> Hi Anthony
>
>
>>> has anybody out there a minimalistic .config to build a minimal guest
>>> kernel image with virtio enabled?
>>>
>>>
>> I usually do a make defconfig, enable the CONFIG_VIRTIO_* options in
>> .config, then do a make oldconfig and answer 'y' t
Balaji Rao <[EMAIL PROTECTED]> writes:
> Hi all!
>
> Earlier it was suggested that we go ahead with emulating Perf Mon Events in
> exposing it to the guest. The serious limitation in this approach is that we
> end up exposing only a small number of events to the guest, even though the
> host ha
On Sat, 2008-02-16 at 10:47 +0200, Avi Kivity wrote:
> Hollis Blanchard wrote:
> > On Wed, 2008-02-13 at 08:58 +0200, Avi Kivity wrote:
> >
> >> It'll need to be built against your kernel tree; please provide a URL.
> >>
> >
> > curl http://penguinppc.org/~hollisb/kvm/kvm-powerpc.mbox | git
Hollis Blanchard wrote:
>> Unfortunately I wasn't able to get an F8 ppc rescue cd ISO to boot with
>> qemu 0.9.0. Can you point me to a working combination?
>>
>
> It's difficult to get anything booting with upstream PowerPC qemu,
> mostly because of the unmaintained firmware they use (calle
On Mon, 2008-02-18 at 22:22 +0200, Avi Kivity wrote:
> Hollis Blanchard wrote:
> >> Unfortunately I wasn't able to get an F8 ppc rescue cd ISO to boot with
> >> qemu 0.9.0. Can you point me to a working combination?
> >>
> >
> > It's difficult to get anything booting with upstream PowerPC q
It seems that we've come up with two reasonable cases where it makes
sense to use these notifiers for InfiniBand/RDMA:
First, the ability to safely to DMA to/from userspace memory with the
memory regions mlock()ed but the pages not pinned. In this case the
notifiers here would seem to suit us wel
Alexander Graf wrote:
> Real mode segments are mere offsets. They get lshifted by 4 (as far as
> I remember) and just added to the offset. SS is on some value here
>
Yes, this is correct.
> 0x00046e60: and$0x,%esp
> 0x00046e66: shl$0x4,%eax
> 0x00046e6
>>> Please post your command line for launching KVM. Make sure you have a
>>> root parameter like "root=/dev/vda1".
>>>
>> the "vda1" thing i didn't know. thanks. will also give it a try - tomorrow.
>>
>> Is "virtio" block device replacing SATA/SCSI - are the SCSI/SA
>>> Please post your command line for launching KVM. Make sure you have a
>>> root parameter like "root=/dev/vda1".
>>>
>> the "vda1" thing i didn't know. thanks. will also give it a try - tomorrow.
>>
>> Is "virtio" block device replacing SATA/SCSI - are the SCSI/SA
29 matches
Mail list logo
