linux-kernel - Re: [PATCH 0/7] KVM: x86: Let the guest write to multiple debug registers with one vmexit

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 09 Mar 2014 09:31:00 +0100
From:	Paolo Bonzini <pbonzini@...hat.com>
To:	Jan Kiszka <jan.kiszka@....de>, linux-kernel@...r.kernel.org
CC:	kvm@...r.kernel.org, alex.williamson@...hat.com,
	mtosatti@...hat.com, gleb@...nel.org
Subject: Re: [PATCH 0/7] KVM: x86: Let the guest write to multiple debug registers
 with one vmexit

Il 09/03/2014 09:15, Jan Kiszka ha scritto:
>> > This looks good now to me from KVM perspective. I was just wondering how
>> > the case is handled that the host used debug registers on the thread the
>> > runs a VCPU? What if I set a hw breakpoint on its userspace path e.g.?
>> > What if I debug the kernel side with kgdb?
> Ah, this part didn't change, we still switch between host and guest
> state on vmentries/exits. All fine!

Yes, that's why sync_dirty_debug_regs is added so early.  Thanks for the 
review.

Paolo
--
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/