lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 07 Jul 2014 14:42:27 +0300 From: Nadav Amit <nadav.amit@...il.com> To: Tang Chen <tangchen@...fujitsu.com>, Gleb Natapov <gleb@...nel.org> CC: mtosatti@...hat.com, kvm@...r.kernel.org, laijs@...fujitsu.com, isimatu.yasuaki@...fujitsu.com, guz.fnst@...fujitsu.com, linux-kernel@...r.kernel.org Subject: Re: [PATCH 4/4] kvm, mem-hotplug: Update apic access page when it is migrated. Tang, Running some (unrelated) tests I see that KVM does not handle APIC base relocation correctly. When the base is changed, kvm_lapic_set_base just changes lapic->base_address without taking further action (i.e., modifying the VMCS apic address in VMX). This patch follows KVM bad behavior by using the constant VMX_APIC_ACCESS_PAGE_ADDR instead of lapic->base_address. Anyhow, I didn't see anything that would make my life (in fixing the lapic base issue) too difficult. Yet, feel free in making it more "fix-friendly". Thanks, Nadav On 7/7/14, 12:52 PM, Tang Chen wrote: > Hi Gleb, > > The guest hang problem has been solved. > > When mmu_notifier is called, I set VMCS APIC_ACCESS_ADDR to the new value > instead of setting it to 0. And only update kvm->arch.apic_access_page in > the next ept violation. > > The guest is running well now. > > I'll post the new patches tomorrow. ;) > > Thanks. > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists