On 20.11.14 20:31, Suresh E. Warrier wrote:
>
>
> On 11/20/2014 11:36 AM, Alexander Graf wrote:
>>
>>
>> On 03.11.14 05:52, Paul Mackerras wrote:
>>> From: "Suresh E. Warrier"
>>>
>>> The kvmppc_vcore_blocked() code does not check for the wait condition
>>> after putting the process on the wai
On 21.11.14 00:45, Cédric Le Goater wrote:
> When being restored from qemu, the kvm_get_htab_header are in native
> endian, but the ptes are big endian.
>
> This patch fixes restore on a KVM LE host. Qemu also needs a fix for
> this :
>
> http://lists.nongnu.org/archive/html/qemu-ppc/2014
On Sat, Nov 15, 2014 at 12:19:10AM -0800, m.smard...@samsung.com wrote:
> From: Mario Smarduch
>
> This patch enables ARMv8 ditry page logging support. Plugs ARMv8 into generic
> layer through Kconfig symbol, and drops earlier ARM64 constraints to enable
> logging at architecture layer.
>
> Sign
On Sat, Nov 15, 2014 at 12:19:08AM -0800, m.smard...@samsung.com wrote:
> From: Mario Smarduch
>
> This patch adds arm64 helpers to write protect pmds/ptes and retrieve
> permissions while logging dirty pages. Also adds prototype to write protect
> a memory slot and adds a pmd define to check f
On Fri, Nov 14, 2014 at 01:54:44PM -0800, Mario Smarduch wrote:
> This patch adds support for handling 2nd stage page faults during migration,
> it disables faulting in huge pages, and dissolves huge pages to page tables.
> In case migration is canceled huge pages are used again.
>
> Resending to
On Thu, Nov 13, 2014 at 05:57:47PM -0800, Mario Smarduch wrote:
> Add support to track dirty pages between user space KVM_GET_DIRTY_LOG ioctl
> calls. We call kvm_get_dirty_log_protect() function to do most of the work.
>
> Reviewed-by: Marc Zyngier
> Signed-off-by: Mario Smarduch
> ---
> arch/
On Thu, Nov 13, 2014 at 05:57:46PM -0800, Mario Smarduch wrote:
> Add support for initial write protection of VM memslots. This patch
> series assumes that huge PUDs will not be used in 2nd stage tables, which is
> always valid on ARMv7.
>
> Signed-off-by: Mario Smarduch
> ---
> arch/arm/include
On Thu, Nov 13, 2014 at 05:57:44PM -0800, Mario Smarduch wrote:
> From: Paolo Bonzini
>
> We now have a generic function that does most of the work of
> kvm_vm_ioctl_get_dirty_log, now use it.
>
> Signed-off-by: Mario Smarduch
> ---
> arch/x86/include/asm/kvm_host.h |3 --
> arch/x86/kvm/K
On Thu, Nov 13, 2014 at 05:57:43PM -0800, Mario Smarduch wrote:
> kvm_get_dirty_log() provides generic handling of dirty bitmap, currently
> reused
> by several architectures. Building on that we intrdoduce
> kvm_get_dirty_log_protect() adding write protection to mark these pages dirty
> for futu
On Thu, Nov 13, 2014 at 05:57:42PM -0800, Mario Smarduch wrote:
> Allow architectures to override the generic kvm_flush_remote_tlbs()
> function via HAVE_KVM_ARCH_TLB_FLUSH_ALL. ARMv7 will need this to
> provide its own TLB flush interface.
>
> Reviewed-by: Marc Zyngier
> Reviewed-by: Paolo Bonzi
On 21/11/2014 22:21, Radim Krčmář wrote:
> Now that ia64 is gone, we can hide deprecated device assignment in x86.
>
> Notable changes:
> - kvm_vm_ioctl_assigned_device() was moved to x86/kvm_arch_vm_ioctl()
>
> The easy parts were removed from generic kvm code, remaining
> - kvm_iommu_(un)ma
caro Signore
cominciamo a vendere iPhone 6 più, solo 450 euro. molto sorprendente
samsung s5, ipad w e b: assr. com
Some hypervisors need MSR auto load/restore feature.
We read MSRs from vm-entry MSR load area which specified by L1,
and load them via kvm_set_msr in the nested entry.
When nested exit occurs, we get MSRs via kvm_get_msr, writing
them to L1`s MSR store area. After this, we read MSRs from vm-exit
M
On 22 November 2014 at 01:50, Mario Smarduch wrote:
> QEMU has a global migration bitmap for all regions initially set
> dirty, and it's updated over iterations with KVM's dirty bitmap. Once
> dirty pages are migrated bits are cleared. If QEMU updates a
> memory region directly I can't see how it'
Hi Eric,
Thanks for your FYI.
On Fri, Nov 21, 2014 at 8:58 PM, Eric Auger wrote:
> Hi Ming,
>
> for your information there is a series written by Antonios (added in CC)
> https://lists.cs.columbia.edu/pipermail/kvmarm/2014-March/008416.html
> exactly on the same topic.
>
> The thread was reactiv
On 11/22/14 11:18, Christoffer Dall wrote:
> On Fri, Nov 21, 2014 at 05:50:43PM -0800, Mario Smarduch wrote:
>> But virtio writes to guest memory directly and that appears to
>> work just fine. I read that code sometime back, and will need to revisit.
>>
> In any case, that's a QEMU implementation
On Fri, Nov 21, 2014 at 05:50:43PM -0800, Mario Smarduch wrote:
> On 11/21/2014 03:19 AM, Christoffer Dall wrote:
> > Hi Mario,
> >
> > On Wed, Nov 19, 2014 at 03:32:31PM -0800, Mario Smarduch wrote:
> >> Hi Laszlo,
> >>
> >> couple observations.
> >>
> >> I'm wondering if access from qemu an
On Fri, Nov 21, 2014 at 07:35:46PM +0100, Paolo Bonzini wrote:
>
>
> On 10/11/2014 09:33, Ard Biesheuvel wrote:
> > This reverts commit 85c8555ff0 ("KVM: check for !is_zero_pfn() in
> > kvm_is_mmio_pfn()") and renames the function to kvm_is_reserved_pfn.
> >
> > The problem being addressed by th
18 matches
Mail list logo
