All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lars Kurth <lars.kurth.xen@gmail.com>
To: Omkar Bolla <omkar.bolla@pathpartnertech.com>
Cc: Julien Grall <julien.grall@arm.com>,
	xen-devel@lists.xensource.com,
	Stefano Stabellini <sstabellini@kernel.org>,
	Oleksandr Andrushchenko <Oleksandr_Andrushchenko@epam.com>
Subject: Re: Xen PV: Sample new PV driver for buffer sharing between domains
Date: Thu, 27 Sep 2018 10:39:36 +0100	[thread overview]
Message-ID: <B9D01323-5CE0-4CAE-9A7C-2B1CE482A833@xenproject.org> (raw)
In-Reply-To: <CAC4nxbvWUpWQcUATQswoaVJfSq8EU7CH6-Jx1VwVGYVeOc0tZw@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1806 bytes --]

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@pathpartnertech.com> 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/ <https://fnordig.de/2016/12/02/xen-a-backend-frontend-driver-example/>
> 
> 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)
> 
> Please suggest me, How to create PV drivers.
> 
> Thanks,
> Omkar B
> 
> 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.
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xenproject.org
> https://lists.xenproject.org/mailman/listinfo/xen-devel


[-- Attachment #1.2: Type: text/html, Size: 3815 bytes --]

[-- Attachment #2: Type: text/plain, Size: 157 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2018-09-27  9:39 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 [this message]
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
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=B9D01323-5CE0-4CAE-9A7C-2B1CE482A833@xenproject.org \
    --to=lars.kurth.xen@gmail.com \
    --cc=Oleksandr_Andrushchenko@epam.com \
    --cc=julien.grall@arm.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.