On 05/22/2011 08:23 AM, Yang, Wei Y wrote:
This patch matches with "[PATCH v2] Enable CPU SMEP feature support for
QEMU-KVM", no changes since v1.
Enable newly documented SMEP (Supervisor Mode Execution Protection) CPU feature
in KVM module.
Intel new CPU supports SMEP (Supervisor Mode Execut
On 05/20/2011 08:59 PM, Blue Swirl wrote:
On Thu, May 19, 2011 at 5:12 PM, Avi Kivity wrote:
> The memory API separates the attributes of a memory region (its size, how
> reads or writes are handled, dirty logging, and coalescing) from where it
> is mapped and whether it is enabled. This all
Hi, Michael.
On Saturday, 21 May 2011 23:39:27 -0400,
Michael Stroucken wrote:
>> I'm doing some testing with KVM Live Migration. SS01 (VMHost) has
>> Debian GNU/Linux 6.0.1 and Defiant (VMHost) has Debian GNU/Linux
>> 5.0.8. Defiant has Linux 2.6.32-15~bpo50+1 and 0.12.5+dfsg-3~bpo50+2,
>> and S
On 05/20/2011 09:16 PM, Blue Swirl wrote:
On Fri, May 20, 2011 at 5:46 PM, Anthony Liguori wrote:
> On 05/20/2011 09:40 AM, Richard Henderson wrote:
>>
>> On 05/20/2011 07:31 AM, Anthony Liguori wrote:
>>>
>>> But is this a characteristic of devices or is this a characteristic of
>>> the chi
On 05/20/2011 05:46 PM, Anthony Liguori wrote:
On 05/20/2011 09:40 AM, Richard Henderson wrote:
On 05/20/2011 07:31 AM, Anthony Liguori wrote:
But is this a characteristic of devices or is this a characteristic
of the chipset/CPU?
Chipset.
So if the chipset only allows accesses that are 64-
On 05/20/2011 05:31 PM, Anthony Liguori wrote:
Several alpha system chips MCE when accessed with incorrect sizes.
E.g. only 64-bit accesses are allowed.
But is this a characteristic of devices or is this a characteristic of
the chipset/CPU?
The chipset is modelled by a MemoryRegion too.
This patch matches with "[PATCH v2] Enable CPU SMEP feature support for
QEMU-KVM", no changes since v1.
Enable newly documented SMEP (Supervisor Mode Execution Protection) CPU feature
in KVM module.
Intel new CPU supports SMEP (Supervisor Mode Execution Protection). SMEP
prevents kernel from e
On Sat, 21 May 2011, Daniel Bareiro wrote:
Hi all!
I'm doing some testing with KVM Live Migration. SS01 (VMHost) has Debian
GNU/Linux 6.0.1 and Defiant (VMHost) has Debian GNU/Linux 5.0.8. Defiant
has Linux 2.6.32-15~bpo50+1 and 0.12.5+dfsg-3~bpo50+2, and SS01 has
Linux 2.6.32-31 and 0.12.5+
> From: Nadav Har'El [mailto:n...@math.technion.ac.il]
> Sent: Saturday, May 21, 2011 4:32 AM
>
> On Fri, May 20, 2011, Tian, Kevin wrote about "RE: [PATCH 07/31] nVMX:
> Introduce vmcs02: VMCS used to run L2":
> > btw, shouldn't you clear recycled VMCS and reset 'cpu' and 'launched'
> > fields?
Hi all!
I'm doing some testing with KVM Live Migration. SS01 (VMHost) has Debian
GNU/Linux 6.0.1 and Defiant (VMHost) has Debian GNU/Linux 5.0.8. Defiant
has Linux 2.6.32-15~bpo50+1 and 0.12.5+dfsg-3~bpo50+2, and SS01 has
Linux 2.6.32-31 and 0.12.5+dfsg-5+squeeze1. Both instalation are 32-bit,
bu
On 21.05.2011, at 19:00, Alexander Graf wrote:
>
> On 21.05.2011, at 18:41, Alexander Graf wrote:
>
>>
>> On 19.05.2011, at 07:22, Paul Mackerras wrote:
>>
>>> On Tue, May 17, 2011 at 02:42:08PM +0300, Avi Kivity wrote:
On 05/17/2011 02:38 PM, Alexander Graf wrote:
>>
>> What wo
On 21.05.2011, at 18:41, Alexander Graf wrote:
>
> On 19.05.2011, at 07:22, Paul Mackerras wrote:
>
>> On Tue, May 17, 2011 at 02:42:08PM +0300, Avi Kivity wrote:
>>> On 05/17/2011 02:38 PM, Alexander Graf wrote:
>
> What would be the path for these patches to get upstream? Would this
On 19.05.2011, at 07:22, Paul Mackerras wrote:
> On Tue, May 17, 2011 at 02:42:08PM +0300, Avi Kivity wrote:
>> On 05/17/2011 02:38 PM, Alexander Graf wrote:
What would be the path for these patches to get upstream? Would this
stuff normally go through Avi's tree? There is a bit
On Tue, 10 May 2011 10:02:11 -0600
Alex Williamson wrote:
> This will allow us to store and load it later.
>
> Signed-off-by: Alex Williamson
> ---
>
> drivers/pci/pci.c | 12 +++-
> include/linux/pci.h | 11 ---
> 2 files changed, 15 insertions(+), 8 deletions(-)
>
> d
On Sat, 2011-05-21 at 16:35 +0300, Pekka Enberg wrote:
> On Sat, May 21, 2011 at 3:10 PM, Cyrill Gorcunov wrote:
> > Without 'ret' usage I get
> >
> > | cyrill@sun kvm $ make
> > | CC virtio/9p.o
> > | virtio/9p.c: In function ‘virtio_p9_wstat’:
> > | virtio/9p.c:448:6: error: variable
On Sat, May 21, 2011 at 3:10 PM, Cyrill Gorcunov wrote:
> Without 'ret' usage I get
>
> | cyrill@sun kvm $ make
> | CC virtio/9p.o
> | virtio/9p.c: In function ‘virtio_p9_wstat’:
> | virtio/9p.c:448:6: error: variable ‘res’ set but not used
> [-Werror=unused-but-set-variable]
> | cc1:
On 05/21/2011 04:08 PM, Cyrill Gorcunov wrote:
> On 05/21/2011 02:55 PM, Sasha Levin wrote:
> ...
void ioport__register(u16 port, struct ioport_operations *ops, int count)
{
- int i;
+ struct ioport_entry *entry;
- for (i = 0; i < count; i++)
- iop
Without 'ret' usage I get
| cyrill@sun kvm $ make
| CC virtio/9p.o
| virtio/9p.c: In function ‘virtio_p9_wstat’:
| virtio/9p.c:448:6: error: variable ‘res’ set but not used
[-Werror=unused-but-set-variable]
| cc1: all warnings being treated as errors
| make: *** [virtio/9p.o] Error 1
On 05/21/2011 02:55 PM, Sasha Levin wrote:
...
>>> void ioport__register(u16 port, struct ioport_operations *ops, int count)
>>> {
>>> - int i;
>>> + struct ioport_entry *entry;
>>>
>>> - for (i = 0; i < count; i++)
>>> - ioport_ops[port + i]= ops;
>>> + entry = ioport_sea
On Sat, 2011-05-21 at 14:31 +0400, Cyrill Gorcunov wrote:
> On 05/21/2011 12:51 PM, Sasha Levin wrote:
> > Currently the ioport implementation is based on a USHRT_MAX length
> > array of ptrs to ioport_operations.
> >
> > Instead, use an interval rbtree to map the ioports to
> > ioport_operations.
On 05/21/2011 12:51 PM, Sasha Levin wrote:
> Currently the ioport implementation is based on a USHRT_MAX length
> array of ptrs to ioport_operations.
>
> Instead, use an interval rbtree to map the ioports to
> ioport_operations.
>
> Signed-off-by: Sasha Levin
> ---
...
> -static struct ioport_op
Currently the ioport implementation is based on a USHRT_MAX length
array of ptrs to ioport_operations.
Instead, use an interval rbtree to map the ioports to
ioport_operations.
Signed-off-by: Sasha Levin
---
tools/kvm/ioport.c | 54 +--
1 files c
Augmentation is started on the pre-rotation node found in the search,
augment the rotated node instead.
Max high is the max of max highs below it, not the max of highs below it.
Signed-off-by: Sasha Levin
---
tools/kvm/util/rbtree-interval.c |6 +++---
1 files changed, 3 insertions(+), 3 de
Hi All,
This is KVM test result against kvm.git
6f1bd0daae731ff07f4755b4f56730a6e4a3c1cb based on kernel 2.6.39-rc7+, and
qemu-kvm.git db8b5127f8a16c251592023de814be248fa84dda.
We found no bug and no fix in our nightly test during the past two weeks.
The qemu [vt-d] bug 754591 exists for a month
24 matches
Mail list logo
