From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pavel Fedin Subject: RE: [PATCH 1/7] KVM: api: add kvm_irq_routing_extended_msi Date: Mon, 06 Jul 2015 16:33:17 +0300 Message-ID: <025301d0b7f0$5210a140$f631e3c0$@samsung.com> References: <1435592237-17924-2-git-send-email-eric.auger@linaro.org> <011f01d0b498$6a17aeb0$3e470c10$@samsung.com> <5596503E.6040902@arm.com> <00fd01d0b7b6$f6cf3550$e46d9ff0$@samsung.com> <559A3C9C.6050302@arm.com> <20150706093026.GA11590@cbox> <559A52E6.5050402@arm.com> <20150706103755.GC11590@cbox> <559A6164.1000401@redhat.com> <559A6527.1040107@arm.com> <20150706120837.GA13530@cbox> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from localhost (localhost [127.0.0.1]) by mm01.cs.columbia.edu (Postfix) with ESMTP id 3DD5057BC1 for ; Mon, 6 Jul 2015 09:21:56 -0400 (EDT) Received: from mm01.cs.columbia.edu ([127.0.0.1]) by localhost (mm01.cs.columbia.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id erwUpFI83kSA for ; Mon, 6 Jul 2015 09:21:54 -0400 (EDT) Received: from mailout2.w1.samsung.com (mailout2.w1.samsung.com [210.118.77.12]) by mm01.cs.columbia.edu (Postfix) with ESMTPS id F2BCF57BBE for ; Mon, 6 Jul 2015 09:21:53 -0400 (EDT) Received: from eucpsbgm2.samsung.com (unknown [203.254.199.245]) by mailout2.w1.samsung.com (Oracle Communications Messaging Server 7.0.5.31.0 64bit (built May 5 2014)) with ESMTP id <0NR2006MPIZJ3S30@mailout2.w1.samsung.com> for kvmarm@lists.cs.columbia.edu; Mon, 06 Jul 2015 14:33:19 +0100 (BST) In-reply-to: <20150706120837.GA13530@cbox> Content-language: ru List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: kvmarm-bounces@lists.cs.columbia.edu Sender: kvmarm-bounces@lists.cs.columbia.edu To: 'Christoffer Dall' , 'Andre Przywara' Cc: eric.auger@st.com, kvm@vger.kernel.org, 'Marc Zyngier' , linux-kernel@vger.kernel.org, 'Paolo Bonzini' , kvmarm@lists.cs.columbia.edu, linux-arm-kernel@lists.infradead.org List-Id: kvmarm@lists.cs.columbia.edu > Just so I'm sure I understand: The way the kernel differentiates between > no-devid and devid==0, is whether or not the devid flag is set, correct? Yes, exactly. Kind regards, Pavel Fedin Expert Engineer Samsung Electronics Research center Russia