From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:39770) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zmf39-0006Yk-Ck for qemu-devel@nongnu.org; Thu, 15 Oct 2015 05:42:16 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Zmf35-0001VV-Cg for qemu-devel@nongnu.org; Thu, 15 Oct 2015 05:42:15 -0400 Received: from mailout1.w1.samsung.com ([210.118.77.11]:37545) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zmf35-0001V2-7V for qemu-devel@nongnu.org; Thu, 15 Oct 2015 05:42:11 -0400 Received: from eucpsbgm1.samsung.com (unknown [203.254.199.244]) by mailout1.w1.samsung.com (Oracle Communications Messaging Server 7.0.5.31.0 64bit (built May 5 2014)) with ESMTP id <0NW9004K89M79Y60@mailout1.w1.samsung.com> for qemu-devel@nongnu.org; Thu, 15 Oct 2015 10:42:07 +0100 (BST) From: Pavel Fedin References: <8ab953090af58ac19d240feb48180b7b6f1f39bb.1444835138.git.p.fedin@samsung.com> <20151014190920-mutt-send-email-mst@redhat.com> <00c201d10727$2b9921f0$82cb65d0$@samsung.com> <20151015120415-mutt-send-email-mst@redhat.com> In-reply-to: <20151015120415-mutt-send-email-mst@redhat.com> Date: Thu, 15 Oct 2015 12:42:06 +0300 Message-id: <00d201d1072d$c1be1e00$453a5a00$@samsung.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit Content-language: ru Subject: Re: [Qemu-devel] [PATCH v4 2/3] hw/pci: Introduce pci_requester_id() List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "'Michael S. Tsirkin'" Cc: 'Paolo Bonzini' , qemu-devel@nongnu.org, 'Peter Maydell' Hello! > Then I realized it's actually the PCI requester ID. > That, in turn, means it can just be a generic PCI API, > e.g. it's also used for assigning pci-x devices. Ok. So, will it be good if i place it in includes/hw/pci.h as static inline, similar to how it was done in v1? Kind regards, Pavel Fedin Expert Engineer Samsung Electronics Research center Russia