From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: [PATCH] x86: allow Dom0 read-only access to IO-APICs Date: Thu, 02 May 2013 08:21:11 +0100 Message-ID: References: <51822BD702000078000D26FB@nat28.tlf.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <51822BD702000078000D26FB@nat28.tlf.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jan Beulich Cc: Andrew Cooper , Konrad Rzeszutek Wilk , Keir Fraser , xen-devel List-Id: xen-devel@lists.xenproject.org On 02/05/2013 08:03, "Jan Beulich" wrote: >> mmio_ro_ranges is not specific to ioapic handling, so its initialisation >> should probably not go to init_ioapic_mappings()? If it is x86 specific (for >> now at least) then it could just go in __start_xen()? > > Can certainly do that - I just followed it originally having been done > by its first user (which now happens to be IO-APIC code). > > If I do so, I shall then also move declaration and definition into x86 > specific files... Makes sense as all uses are under arch/x86 anyhow. -- Keir