From: marc.zyngier@arm•com (Marc Zyngier)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH V12 3/7] dma: add Qualcomm Technologies HIDMA management driver
Date: Fri, 15 Jan 2016 18:08:51 +0000 [thread overview]
Message-ID: <569935B3.4090004@arm.com> (raw)
In-Reply-To: <56992FE8.4000606@codeaurora.org>
On 15/01/16 17:44, Sinan Kaya wrote:
>>>
[...]
>> You may want to drop the "hypervisor" designation, BTW, because this has
>> no real connection to virtualisation.
>>
>
> Would you use host/guest relationship?
Not even that. This is a host/user relationship, as VFIO is in no way
virtualisation specific. It just gives you a way to make a device
accessible to userspace. KVM is just a specialised instance of a more
generic problem.
>
>>>
>>> Once the guest machine is shutdown, VFIO driver still owns the channel device. It can
>>> assign the device to another guest machine.
>>>
>>>> - Does the HYP side requires any context switch (and how is that done)?
>>> No communication is needed.
>>>
>>>> - What makes it safe?
>>> No communication is needed.
>>>
>>>>
>>>> Without any of this information (and pointer to the code to back it up),
>>>> I'm very reluctant to take any of this.
>>>
>>> Please let me know what exactly is not clear.
>>>
>>> You don't write a virtualization driver for 8139too driver. The driver works whether it is running in the
>>> guest machine or the hypervisor.
>>
>> Exactly. No hypervisor code needed whatsoever. So please get rid of this
>> hypervisor nonsense! ;-)
>>
>
> I need the management driver for administrative purposes and common initialization.
> I like the split SW design as it follows the HW design too.
I have no problem with the split design (whatever floats your boat),
more with the terminology which I find very confusing. It would be a lot
better if you stuck with management (host) and client (user), or some
other general terminology.
Thanks,
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2016-01-15 18:08 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-11 14:45 [PATCH v12 0/7] dma: add Qualcomm Technologies HIDMA driver Sinan Kaya
2016-01-11 14:45 ` [PATCH V12 1/7] dma: qcom_bam_dma: move to qcom directory Sinan Kaya
2016-01-11 14:45 ` [PATCH V12 2/7] dma: hidma: Add Device Tree support Sinan Kaya
2016-01-15 15:16 ` Mark Rutland
2016-01-15 15:30 ` Mark Rutland
2016-01-15 17:05 ` Sinan Kaya
2016-01-18 11:39 ` Mark Rutland
2016-01-15 16:49 ` Sinan Kaya
2016-01-18 11:49 ` Mark Rutland
2016-01-18 14:04 ` Sinan Kaya
2016-01-11 14:45 ` [PATCH V12 3/7] dma: add Qualcomm Technologies HIDMA management driver Sinan Kaya
2016-01-15 14:56 ` Mark Rutland
2016-01-15 15:12 ` Sinan Kaya
2016-01-15 15:22 ` Mark Rutland
2016-01-15 17:16 ` Sinan Kaya
2016-01-15 17:32 ` Marc Zyngier
2016-01-15 22:47 ` Sinan Kaya
2016-01-18 9:06 ` Marc Zyngier
2016-01-22 18:38 ` Sinan Kaya
2016-01-15 15:14 ` Marc Zyngier
2016-01-15 15:36 ` Mark Rutland
2016-01-15 16:01 ` Sinan Kaya
2016-01-20 22:18 ` Sinan Kaya
2016-01-15 15:40 ` Sinan Kaya
2016-01-15 17:28 ` Marc Zyngier
2016-01-15 17:44 ` Sinan Kaya
2016-01-15 18:08 ` Marc Zyngier [this message]
2016-01-11 14:45 ` [PATCH V12 4/7] dma: add Qualcomm Technologies HIDMA channel driver Sinan Kaya
2016-01-11 14:45 ` [PATCH V12 5/7] dma: qcom_hidma: implement lower level hardware interface Sinan Kaya
2016-01-11 14:45 ` [PATCH V12 6/7] dma: qcom_hidma: add debugfs hooks Sinan Kaya
2016-01-11 14:45 ` [PATCH V12 7/7] dma: qcom_hidma: add support for object hierarchy Sinan Kaya
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=569935B3.4090004@arm.com \
--to=marc.zyngier@arm$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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