From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH 07 of 19] Move kvm_create_phys_mem to libkvm-x86.c Date: Sun, 04 Nov 2007 09:29:15 +0200 Message-ID: <472D74CB.8050602@qumranet.com> References: <8e77064ea82d0b7fbd8b.1194027896@thinkpad> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org, kvm-ppc-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org To: Jerone Young Return-path: In-Reply-To: <8e77064ea82d0b7fbd8b.1194027896@thinkpad> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: kvm.vger.kernel.org Jerone Young wrote: > # HG changeset patch > # User Jerone Young > # Date 1194027872 18000 > # Node ID 8e77064ea82d0b7fbd8bb77429bbfd62f99c00f6 > # Parent 02f38e54018070bafd501df846147f4ae7661109 > Move kvm_create_phys_mem to libkvm-x86.c > > This patch moves kvm_create_phys_mem to libkvm-x86.c > > Creating physical memory isn't arch specific (though a few details are). Why is this made arch specific? -- Any sufficiently difficult bug is indistinguishable from a feature. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/