From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 3B247C433F5 for ; Tue, 26 Apr 2022 11:18:25 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=sMJd+RyfaUzqbq8R3SYQrC/hyLd8sJwcoK/8xoidfHY=; b=4VWU6o0uSP6AD+ mtonydYkRaomj+0urw1w5lFHCXrACqGnb2XKJ9bap3B/o7UL3qvtnwQd3VgenC6FkfjQwxgrhAMtJ y3v88TC/E9uaxmFE8cMCXi7oJNYCSqjebaXdvk5bDGenJS72KidDyvAS0eggpuvsOQVZ0x131zrRh GaDcJdAbSRQ5GBGBRIRhKMdbGyXvqzZdruOJMP7LAiD4oH5EP703lvq19XrJ/7RRgTcT/bTj+Xz8e DrEp5Z0EqhAkTmS0QjasH5X6U6vFv0wZrldJ7JsA0UUUt9GYkbKomykDiQPLUCdUXC/MqbQeTCf4f lvXaeH3/p8PRVfzb6uBg==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1njJC5-00E45S-2b; Tue, 26 Apr 2022 11:17:21 +0000 Received: from mail.skyhub.de ([2a01:4f8:190:11c2::b:1457]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1njJC0-00E41u-9b for linux-arm-kernel@lists.infradead.org; Tue, 26 Apr 2022 11:17:18 +0000 Received: from zn.tnic (p5de8eeb4.dip0.t-ipconnect.de [93.232.238.180]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.skyhub.de (SuperMail on ZX Spectrum 128k) with ESMTPSA id 333FA1EC0503; Tue, 26 Apr 2022 13:17:01 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alien8.de; s=dkim; t=1650971821; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:in-reply-to:in-reply-to: references:references; bh=0/pzm9e2iDycI7rO928zqJLiV9GuD5I4xPzZfSe633g=; b=QKn7p9c+Xx58HkrgfK0vaZ0Hq8RwnOhXDyfVc1uhejI5I0GIt/UsYcC87wFSHsiwlfBDip KIXZVbnVxB9vh/6WhJoc0woZlZd+mvo/f1R0qgbcG+6qGZNU8S4gmoJ+P8RlLJPQXSVns4 hu2B8sKa65pKnilCIQ3ZuI1qd8xMtrw= Date: Tue, 26 Apr 2022 13:16:58 +0200 From: Borislav Petkov To: Juergen Gross Cc: Oleksandr , Christoph Hellwig , Boris Ostrovsky , Stefano Stabellini , xen-devel@lists.xenproject.org, x86@kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Dave Hansen , Andy Lutomirski , Peter Zijlstra , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Julien Grall , Oleksandr Tyshchenko , "Michael S. Tsirkin" , Tom Lendacky Subject: Re: [PATCH V1 3/6] xen/virtio: Add option to restrict memory access under Xen Message-ID: References: <6c5042fe-dafc-eb4f-c1fa-03b0faf252de@gmail.com> <147f68f6-7d67-1884-bd14-5040639b3396@suse.com> <67c7460a-3001-35a6-8e5b-f367270b257a@gmail.com> <7d89848a-3a1c-415d-957a-564ffdd3712d@suse.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220426_041716_518998_5AD47B33 X-CRM114-Status: GOOD ( 11.14 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Tue, Apr 26, 2022 at 11:36:40AM +0200, Juergen Gross wrote: > As the suggestion was to add another flag this wouldn't be a problem IMO. We had a problem already with adding one flag would break the same flag on the other guest type. That's why we added cc_vendor too. So it can be tricky. > platform_has() doesn't seem too bad IMO. > > I will write a patch for starting the discussion. Yeah, I guess such a proposal would need a wider audience - maybe CC linux-arch... Thx. -- Regards/Gruss, Boris. https://people.kernel.org/tglx/notes-about-netiquette _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel