linux-kernel - Re: [PATCH 00/34] arch: barrier cleanup + __smp

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: <20151230.154646.596597479469584255.davem@davemloft.net>
Date:	Wed, 30 Dec 2015 15:46:46 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	mst@...hat.com
Cc:	linux-kernel@...r.kernel.org, peterz@...radead.org, arnd@...db.de,
	linux-arch@...r.kernel.org, andrew.cooper3@...rix.com,
	virtualization@...ts.linux-foundation.org,
	stefano.stabellini@...citrix.com
Subject: Re: [PATCH 00/34] arch: barrier cleanup + __smp_xxx barriers for
 virt

From: "Michael S. Tsirkin" <mst@...hat.com>
Date: Wed, 30 Dec 2015 14:58:19 +0200

> -. Patch 1 documents the __smp APIs, and explains why they are
>    useful for virt

If virt is doing things like interacting with descriptors that are
shared with a (potentially SMP) host, why don't we just annotate those
specific cases?

The other memory barriers in the kernel do not matter for SMP'ness
when build UP.
--
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/