linux-kernel - Re: [PATCH 2/5 V5] Add functions to check if the host has stopped the vm

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]

Message-ID: <4EE8DD53.5010408@redhat.com>
Date:	Wed, 14 Dec 2011 19:30:59 +0200
From:	Avi Kivity <avi@...hat.com>
To:	Eric B Munson <emunson@...bm.net>
CC:	Marcelo Tosatti <mtosatti@...hat.com>, mingo@...hat.com,
	hpa@...or.com, arnd@...db.de, ryanh@...ux.vnet.ibm.com,
	aliguori@...ibm.com, jeremy.fitzhardinge@...rix.com,
	levinsasha928@...il.com, Jan Kiszka <jan.kiszka@...mens.com>,
	kvm@...r.kernel.org, linux-arch@...r.kernel.org, x86@...nel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/5 V5] Add functions to check if the host has stopped
 the vm

On 12/14/2011 07:11 PM, Eric B Munson wrote:
> > > > 
> > > > If I understand (please correct me if this is wrong) because this is only
> > > > called from the watchdog, which disables preemption, we should be protected
> > > > from something else writing to these flags.
> > >
> > > The host can write, but in that case race is harmless.
> > 
> > Why is it harmless?  You don't know what's in those other flags.
> > 
> > -- 
> > error compiling committee.c: too many arguments to function
> > 
>
> Currently there is only one other flag in this byte (PVCLOCK_TSC_STABLE_BIT)
> and it isset once in kvmclock_init().  It is highly unlikely that the vm will
> be stopped during this init and have the flag clobbered.  After the tsc stable
> bit is written in the init, the field is read only outside of the guest paused
> code.

Let's not lay minefields for us later to step into.  Making this a
cpu-local atomic (irq safe but not smp safe) is simple and easy,
somehting like __this_cpu_and().

-- 
error compiling committee.c: too many arguments to function

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