From: Juergen Gross <jgross@suse.com>
To: Omkar Bolla <omkar.bolla@pathpartnertech.com>,
Oleksandr_Andrushchenko@epam.com
Cc: andr2000@gmail.com, lars.kurth.xen@gmail.com,
Julien Grall <julien.grall@arm.com>,
xen-devel@lists.xensource.com,
Stefano Stabellini <sstabellini@kernel.org>
Subject: Re: Xen PV: Sample new PV driver for buffer sharing between domains
Date: Thu, 27 Sep 2018 13:03:11 +0200 [thread overview]
Message-ID: <d130b853-0e33-ecb7-5598-d99791a5f2bf@suse.com> (raw)
In-Reply-To: <CAC4nxbvh6LA=t2iEdiw2UrqrQP3Zf2NtRcViJ1YNGZkyLZqYHg@mail.gmail.com>
On 27/09/2018 12:35, Omkar Bolla wrote:
> Hi,
>
> Sorry, I forgot, I used code from github chapter [2] from that link, and
> I just changed name "mydevice" to "vdevb"
Okay.
>
>> 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?
I guess you have your frontend already loaded when running the
script creating the Xenstore entries?
This would explain the problem: as soon as the entries are written
the frontend will react. At this point the access rights are not setup
properly, this is done a little bit later in the script.
Possible solutions are to either load the frontend driver only after
setting up the Xenstore entries, or to pause the domain while doing
so and unpause it afterwards (or start the domain paused, create the
Xenstore entries, and unpause the domain).
The really correct way to do it would be to setup Xenstore in a single
transaction (write all the entries and set access rights).
> Any thing that I have to do/change in xenbits xen-4.8 sources code, to
> add new PV device?
Only if you want to include domain config file entries for your 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?
This was just a question to learn how Xenstore is being initialized
in your scenario.
>
>> If not you need to setup the Xenstore nodes manually.
> Setup manually Xenstore means, using commands?
Yes, like your script does.
Juergen
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-09-27 11:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-27 5:44 Xen PV: Sample new PV driver for buffer sharing between domains Omkar Bolla
2018-09-27 9:39 ` Lars Kurth
2018-09-27 10:07 ` Oleksandr Andrushchenko
2018-09-27 10:16 ` Juergen Gross
2018-09-27 10:20 ` Oleksandr Andrushchenko
2018-09-27 10:34 ` Julien Grall
2018-09-27 10:35 ` Omkar Bolla
2018-09-27 11:03 ` Juergen Gross [this message]
2018-09-28 12:55 ` Omkar Bolla
2018-09-28 13:42 ` Juergen Gross
2018-10-02 10:03 ` Omkar Bolla
2018-10-03 9:53 ` Julien Grall
2018-10-08 9:12 ` Omkar Bolla
2018-10-08 10:30 ` Julien Grall
2018-10-17 12:24 ` Omkar Bolla
2018-10-31 19:41 ` Julien Grall
2018-11-01 9:15 ` Omkar Bolla
2018-11-01 21:49 ` Julien Grall
2018-11-02 5:25 ` Omkar Bolla
2018-11-02 8:47 ` Wei Liu
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=d130b853-0e33-ecb7-5598-d99791a5f2bf@suse.com \
--to=jgross@suse.com \
--cc=Oleksandr_Andrushchenko@epam.com \
--cc=andr2000@gmail.com \
--cc=julien.grall@arm.com \
--cc=lars.kurth.xen@gmail.com \
--cc=omkar.bolla@pathpartnertech.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.