Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758391AbbGHMu3 (ORCPT ); Wed, 8 Jul 2015 08:50:29 -0400 Received: from smtp.citrix.com ([66.165.176.89]:42752 "EHLO SMTP.CITRIX.COM" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753073AbbGHMu1 (ORCPT ); Wed, 8 Jul 2015 08:50:27 -0400 X-IronPort-AV: E=Sophos;i="5.15,431,1432598400"; d="scan'208";a="279072346" Message-ID: <559D1C8E.3040704@citrix.com> Date: Wed, 8 Jul 2015 13:50:22 +0100 From: David Vrabel User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.7.0 MIME-Version: 1.0 To: Boris Ostrovsky , , CC: , , , , , , , , , , Subject: Re: [Xen-devel] [PATCH 0/6] 32-bit PVH domU support References: <1436240065-10813-1-git-send-email-boris.ostrovsky@oracle.com> In-Reply-To: <1436240065-10813-1-git-send-email-boris.ostrovsky@oracle.com> Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit X-DLP: MIA1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1014 Lines: 25 On 07/07/15 04:34, Boris Ostrovsky wrote: > > A set of PVH-related patches. > > The first patch is x86-64 ABI fix for PVH guests. The second is a small update > that removes redundant memset (both on PV and PVH code paths) > > The rest is to enable non-privileged 32-bit PVH guests. This requires hypervisor > patches from > http://lists.xenproject.org/archives/html/xen-devel/2015-06/msg04817.html The more I look at the PVH entry point into Linux, and the less I like it -- it's much too PV-like instead of HVM-like. However, this 32-bit support doesn't make it much worse and until there's a decision on the longterm future of PVH I'm inclined to accept it (provided the hypervisor side is accepted) to make it easier to continue working on PVH support. David -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/