From mboxrd@z Thu Jan 1 00:00:00 1970 From: Cyrill Gorcunov Subject: Re: [PATCH 1/2] kvm tools: Fix IRQ assignments Date: Fri, 06 May 2011 12:16:48 +0400 Message-ID: <4DC3AE70.1080801@gmail.com> References: <1304666795-15251-1-git-send-email-levinsasha928@gmail.com> <1304667363.10534.5.camel@lappy> <1304668876.10534.9.camel@lappy> <4DC3AC68.10208@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Sasha Levin , mingo@elte.hu, asias.hejun@gmail.com, prasadjoshi124@gmail.com, kvm@vger.kernel.org To: Pekka Enberg Return-path: Received: from mail-ew0-f46.google.com ([209.85.215.46]:47743 "EHLO mail-ew0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753221Ab1EFIQx (ORCPT ); Fri, 6 May 2011 04:16:53 -0400 Received: by ewy4 with SMTP id 4so894371ewy.19 for ; Fri, 06 May 2011 01:16:52 -0700 (PDT) In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: On 05/06/2011 12:10 PM, Pekka Enberg wrote: > On Fri, May 6, 2011 at 11:08 AM, Cyrill Gorcunov wrote: >> Yes, that is what we do, and it seems to be the "right" way how sane bios >> should behave, same time (i might be wrong since I didn't checked this >> part of kernel sources) the kernel might scan memory for pci configs and >> read pis/irq directly from there, I think this way kernel workaround broken >> bioses but now sure if we should rely on this feature. > > That's not a problem, though, is it? As long as you use the "device > tree" to set up the PCI configs as well, it's irrelevant where the > kernel picks them up, no? Yeah, if we have own "tracking" tool to allocate irqs/pins we put consistent data into both mptable and pci config space. Which of course means we need some more code for allocator/tracker ;) -- Thanks, Cyrill