Xen project Mailing List

Hi,

Sorry, I forgot, I used code from github chapter [2] from that link, and

I just changed name "mydevice" to "vdevb"

> Error 13 is EACCESS. I guess the access rights of the Xenstore nodes
> are not sufficient to write the needed entries.
Where I have to provide access rights, i.e from Kernel code or from from command line in domain-0 or modify in xen source?

Any thing that I have to do/change in xenbits xen-4.8 sources code, to add new PV device?

> Did you modify Xen tools (xl/libxl) for adding the new device type?

No, is it needed to modify some thing in xl/libxl for adding new device type?

> If not you need to setup the Xenstore nodes manually.

Setup manually Xenstore means, using commands?

Thanks,

Omkar B

On Thu, Sep 27, 2018 at 3:50 PM Oleksandr Andrushchenko <Oleksandr_Andrushchenko@xxxxxxxx> wrote:

On 09/27/2018 01:16 PM, Juergen Gross wrote:
> On 27/09/2018 12:07, Oleksandr Andrushchenko wrote:
>> Hi,
>> On 09/27/2018 12:39 PM, Lars Kurth wrote:
>>> Adding a few people who have recently been working on PV drivers, as
>>> well as Julien
>>> Lars
>>>
>>>> On 27 Sep 2018, at 06:44, Omkar Bolla
>>>> <omkar.bolla@xxxxxxxxxxxxxxxxxxx
>>>> <mailto:omkar.bolla@xxxxxxxxxxxxxxxxxxx>> wrote:
>>>>
>>>> Hi,
>>>>
>>>> I am using Debian as Domain-0 and Debian as Domain-U on Hikey960
>>>> platform(ARMv8) and using Xen-4.8 stable release. Here I want to
>>>> create a PV frontend and backend to share memory between Domain-0 and
>>>> Domain-U.
>>>>
>>>>
>>>>
>>>> I used below link to create frontend and backend,
>>>> https://fnordig.de/2016/12/02/xen-a-backend-frontend-driver-example/
>> The link above has another link to github [1] with 2 chapters. And it
>> looks like you have
>> already modified the sources ("mydevice" -> "vdevb" at least).
>> So, what are the sources you are using?
>>
>> You could probably take a look at the relatively small vkbd frontend
>> driver [2]
>> to get some hints.
>>>> But I am facing below errors while adding device vdevb to xenstore.
>>>> Below errors I am getting from xenbus_switch_state().
>>>> vdevb vdevb-0: failed to write error node for device/vdevb/0 (13
>>>> writing new state)
> Error 13 is EACCESS. I guess the access rights of the Xenstore nodes
> are not sufficient to write the needed entries.
>
> Did you modify Xen tools (xl/libxl) for adding the new device type?
> If not you need to setup the Xenstore nodes manually.
There is a script [1] which comes with the example implementation,
so I believe Omkar uses it with "mydevice" -> "vdevb" change
>
>
> Juergen
[1]
https://github.com/badboy/xen-split-driver-example/blob/master/chapter02/activate.sh

This message contains confidential information and is intended only for the individual(s) named. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this mail and attached file/s is strictly prohibited. Please notify the sender immediately and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secured or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission.

Re: [Xen-devel] Xen PV: Sample new PV driver for buffer sharing between domains