Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755703AbZFRS2R (ORCPT ); Thu, 18 Jun 2009 14:28:17 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752587AbZFRS2G (ORCPT ); Thu, 18 Jun 2009 14:28:06 -0400 Received: from mga11.intel.com ([192.55.52.93]:64665 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752541AbZFRS2F convert rfc822-to-8bit (ORCPT ); Thu, 18 Jun 2009 14:28:05 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.42,246,1243839600"; d="scan'208";a="467623931" From: "Yu, Fenghua" To: "'Chris Wright'" CC: "'David Woodhouse'" , "'Linus Torvalds'" , "'Stephen Rothwell'" , "'Andrew Morton'" , "'Ingo Molnar'" , "'Christopher Wright'" , "Kay, Allen M" , "'iommu'" , "'lkml'" Date: Thu, 18 Jun 2009 11:28:06 -0700 Subject: RE: [PATCH 1/2] IOMMU Identity Mapping Support: iommu_identity_mapping definition Thread-Topic: [PATCH 1/2] IOMMU Identity Mapping Support: iommu_identity_mapping definition Thread-Index: AcnwQLzCJyXyAkxXR/yXmqkW09C/4wAAGL9w Message-ID: References: <20090327212241.234500000@intel.com> <20090327212321.070229000@intel.com> <20090416001957.GA1527@linux-os.sc.intel.com> <1240135508.3589.75.camel@macbook.infradead.org> <20090513231351.GA22386@linux-os.sc.intel.com> <1242314271.3393.11.camel@macbook.infradead.org> <20090514175944.GA5168@linux-os.sc.intel.com> <20090618180514.GA24082@linux-os.sc.intel.com> <20090618181335.GB19771@sequoia.sous-sol.org> In-Reply-To: <20090618181335.GB19771@sequoia.sous-sol.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 805 Lines: 20 >> >> The first patch defines iommu_identity_mapping varialbe which controls >the >> identity mapping code and is 0 by default. > >The only real difference between "pt" and "identity" is hardware support. >We should have a single value we don't have to tell users to do different >things depending on their hardware (they won't even know what they have) >to achieve the same result. Technically keeping two separate options in base kernel might be clear and easy to understand. A distro might merge them together or have other usage model. Thanks. -Fenghua -- 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/