qemu-arm.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Sinan Kaya <okaya@codeaurora.org>
To: Auger Eric <eric.auger@redhat.com>,
	Shanker Donthineni <shankerd@codeaurora.org>,
	qemu-arm <qemu-arm@nongnu.org>,
	qemu-devel <qemu-devel@nongnu.org>,
	Peter Maydell <peter.maydell@linaro.org>,
	Alex Williamson <alex.williamson@redhat.com>
Cc: Philip Elcan <pelcan@codeaurora.org>,
	Alexander Graf <agraf@suse.de>,
	Vikram Sethi <vikrams@codeaurora.org>,
	Eric Auger <eric.auger@linaro.org>
Subject: Re: [Qemu-arm] [Qemu-devel] [PATCH v2] hw/vfio/platform: Add Qualcomm Technologies, Inc HIDMA device support
Date: Thu, 18 Aug 2016 09:52:41 -0400	[thread overview]
Message-ID: <3fef4cd0-75df-0bb1-bd7d-dd6a966a05b1@codeaurora.org> (raw)
In-Reply-To: <f928f18f-22c5-4d8f-33c9-2701a66ab2bd@redhat.com>

On 8/18/2016 5:37 AM, Auger Eric wrote:
> Some general comments:
> - I preferred the previous series organization where we had the creation
> of the VFIO device first and its sysbus-fdt dynamic instantiation in a
> separate patch.
> 
> Peter requested sysbus-fdt stops growing and advised to split the fine
> into generic helpers and specific dt creation functions in separate
> files. This sounds the right moment to do it with looming new VFIO devices.
> 
> (*) Also I am now reconsidering the relevance of creating specific VFIO
> devices per compat string. At the begining of VFIO QEMU integration
> history we made that choice, advised by Alex (Graf), considering the
> QEMU VFIO device could not be generic. With a little more experience now
> we could see the specialization is currently done in the dt creation
> function (sysbus-fdt) and in the kernel reset module. So I would now
> advocate using a non abstract base VFIO device that could be
> instantiated passing its compat string as property. Creating
> hw/vfio/qcom-hidma.c and include/hw/vfio/vfio-qcom-hidma.h then would
> become useless. Alex, what is your feeling now?
> 
> I think the split of sysbus-fdt and (*) - if approoved -  shall be
> considered before introducing a new QEMU VFIO device. Are you willing to
> work on it?

I really like generic device approach. It would save a ton of burden from
developers.

If somebody needs a specialized device, they can do so. For simple objects
that just needs a compat string, it doesn't make sense to create a driver
every single time.

Similarly, there is generic PCI host driver in the Linux kernel that works
for systems that is CAM or ECAM compliant. If somebody needs to do more,
they can implement their own PCI host driver too. 

We are really looking for the same model.

I'm interested in virtualization of platform SATA and HIDMA devices. The
only difference between these are the compatible strings. 

Why submit a new SATA AHCI driver for QEMU just to set the compat string?

-- 
Sinan Kaya
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc.
Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.

  reply	other threads:[~2016-08-18 13:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-14 15:42 [Qemu-devel] [PATCH v2] hw/vfio/platform: Add Qualcomm Technologies, Inc HIDMA device support Shanker Donthineni
2016-08-15 16:03 ` Peter Maydell
2016-08-15 16:47   ` [Qemu-arm] " Sinan Kaya
2016-08-18  9:37 ` [Qemu-arm] [Qemu-devel] " Auger Eric
2016-08-18 13:52   ` Sinan Kaya [this message]
2016-08-18 22:35   ` Alexander Graf
2016-08-19 11:43     ` Auger Eric
2016-08-19 16:52       ` Shanker Donthineni

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3fef4cd0-75df-0bb1-bd7d-dd6a966a05b1@codeaurora.org \
    --to=okaya@codeaurora.org \
    --cc=agraf@suse.de \
    --cc=alex.williamson@redhat.com \
    --cc=eric.auger@linaro.org \
    --cc=eric.auger@redhat.com \
    --cc=pelcan@codeaurora.org \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=shankerd@codeaurora.org \
    --cc=vikrams@codeaurora.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).