On 09/27/2018 06:06 PM, Dario Faggioli wrote:
On Thu, 2018-09-27 at 16:09 +0100, Julien Grall wrote:
Hi,
Hi Dario,
On 09/27/2018 03:32 PM, Dario Faggioli wrote:
On Thu, 2018-09-27 at 15:15 +0200, Milan Boberic wrote:
In one of your e-mail, you wrote:
"Well, our implementation of RCU re
Hi,
thank you for explanation, links and advices. I'm gonna go through all
that literature.
Best regards!
On Thu, Sep 27, 2018 at 7:06 PM Dario Faggioli wrote:
>
> On Thu, 2018-09-27 at 16:09 +0100, Julien Grall wrote:
> > Hi Dario,
> >
> Hi,
>
> > On 09/27/2018 03:32 PM, Dario Faggioli wrote:
>
On Thu, 2018-09-27 at 16:09 +0100, Julien Grall wrote:
> Hi Dario,
>
Hi,
> On 09/27/2018 03:32 PM, Dario Faggioli wrote:
> > On Thu, 2018-09-27 at 15:15 +0200, Milan Boberic wrote:
> > >
> In one of your e-mail, you wrote:
>
> "Well, our implementation of RCU requires that, from time to time,
>
Hi Dario,
On 09/27/2018 03:32 PM, Dario Faggioli wrote:
On Thu, 2018-09-27 at 15:15 +0200, Milan Boberic wrote:
Hi,
I applied patch and vwfi=native and everything works fine, I can
create and destroy guest domain as many times as I want.
Ok, now that we know it works, what do you guys prefer?
On Thu, 2018-09-27 at 15:15 +0200, Milan Boberic wrote:
> Hi,
> I applied patch and vwfi=native and everything works fine, I can
> create and destroy guest domain as many times as I want.
>
Ok, now that we know it works, what do you guys prefer?
Stefano? Julien? I know it's not strictly an ARM-on
On Thu, 2018-09-27 at 15:15 +0200, Milan Boberic wrote:
> Hi,
> I applied patch and vwfi=native and everything works fine, I can
> create and destroy guest domain as many times as I want.
>
> I have to ask, will this patch have any impact on performance (I will
> test it later, but I just need you
Hi,
I applied patch and vwfi=native and everything works fine, I can
create and destroy guest domain as many times as I want.
I have to ask, will this patch have any impact on performance (I will
test it later, but I just need your opinions)?
And what this patch exactly do? I need to fully underst
On Tue, 2018-09-25 at 19:49 +0200, Dario Faggioli wrote:
> [Adding a few people to the Cc-list. See below...]
> On Tue, 2018-09-25 at 12:15 +0100, Julien Grall wrote:
> > On 09/25/2018 10:02 AM, Dario Faggioli wrote:
> > > On Mon, 2018-09-24 at 22:46 +0100, Julien Grall wrote:
> > > >
> My knowled
[Adding a few people to the Cc-list. See below...]
On Tue, 2018-09-25 at 12:15 +0100, Julien Grall wrote:
> Hi Dario,
>
Hi,
> On 09/25/2018 10:02 AM, Dario Faggioli wrote:
> > On Mon, 2018-09-24 at 22:46 +0100, Julien Grall wrote:
> > >
> > > Per my understanding of call_rcu, the calls will be
Reply for Julien,
yes, my platform have 4 CPUs it's UltraZed-EG board with carrier card.
I use only 2 CPUs, one for dom0 which is PetaLinux and one for domU
which is bare-metal application that blinks LED on the board (I use it
to measure jitter with oscilloscope), other two CPUs are unused (in
idl
Hi Dario,
On 09/25/2018 10:02 AM, Dario Faggioli wrote:
On Mon, 2018-09-24 at 22:46 +0100, Julien Grall wrote:
On 09/21/2018 05:20 PM, Dario Faggioli wrote:
What I'm after, is how log, after domain_destroy(),
complete_domain_destroy() is called, and whether/how it relates the
the
grace period
On 09/25/2018 11:12 AM, Milan Boberic wrote:
Hello guys,
Hi Milan,
mapping on my system is:
dom0 have one vCPU and it is pinned on pCPU0
domU also have one vCPU and it's pinned for pCPU2
Your platform has 4 CPUs, right? What does the other do? Just sitting in
the idle loop?
I removed
Hello guys,
mapping on my system is:
dom0 have one vCPU and it is pinned on pCPU0
domU also have one vCPU and it's pinned for pCPU2
I removed only vwfi=native and everything works fine. I can destroy
and create a guest as many times as I want with out any error (still
using sched=null).
These are
On Mon, 2018-09-24 at 22:46 +0100, Julien Grall wrote:
> On 09/21/2018 05:20 PM, Dario Faggioli wrote:
> >
> > What I'm after, is how log, after domain_destroy(),
> > complete_domain_destroy() is called, and whether/how it relates the
> > the
> > grace period idle timer we've added in the RCU code
Hi,
On 09/21/2018 05:20 PM, Dario Faggioli wrote:
[Adding Julien as well.
Julien, this seems related to the RCU issue we fought on ARM when using
Credit2, although this is null, but it's being even more weird...]
On Fri, 2018-09-21 at 16:14 +0200, Milan Boberic wrote:
Hey,
yes, I can see prin
[Adding Julien as well.
Julien, this seems related to the RCU issue we fought on ARM when using
Credit2, although this is null, but it's being even more weird...]
On Fri, 2018-09-21 at 16:14 +0200, Milan Boberic wrote:
> Hey,
> yes, I can see prink's outputs on console and in xl dmesg. Also added
Hey,
yes, I can see prink's outputs on console and in xl dmesg. Also added
timestamps, here are the results (created and destroyed domU a few
times, just to get more values), this is from xl dmesg:
NULL SCHEDULER - Not stressed PetaLinux host domain.
(XEN) t=218000327743:End of a domain_destroy f
Hey,
Sorry for not having followed up. I was (and still am) planning to, but
am also a bit busy.
On Thu, 2018-09-20 at 15:04 +0200, Milan Boberic wrote:
> I ran some more tests and managed to successfully create and destroy
> domU as many times as I want, without any delay between destroy and
> c
I ran some more tests and managed to successfully create and destroy
domU as many times as I want, without any delay between destroy and
create.
I added:
printk("End of a domain_destroy function");
in domain_destroy function and
printk("End of a complete_domain_destroy function"); in
complete_dom
Thank you for taking your time to deal with this problem.
I did more testing just to be sure and I also measured time (using
stopwatch on my phone which isn't precise at all, just wanted You to
get the feeling of what time intervals are we talking about).
Yes, I can confirm that that situation actu
On Thu, 2018-09-13 at 17:18 +0200, Milan Boberic wrote:
> Commits are there and I will definitely continue with 4.10 version.
> But it didn't solve my problem entirely.
>
> I create my bare-metal application (with xl create) and destroy it
> with xl destroy (it disappears from xl list) and when I
I'm sorry for html and dropping xen-devel and dropping other CCs,
missed to read the rules.
I tried 4.10 version and checked for commits you asked in earlier reply.
2b936ea7b "xen: RCU: avoid busy waiting until the end of grace period."
38ad8151f "xen: RCU: don't let a CPU with a callback go idle.
Hi,
I implemented Xen Hypervisor 4.9.2 on UltraZed-EG board with carrier card
following these steps:
1.) installed petalinux on Ubuntu 16.04
2.) dowloaded UltraZed-EG IO Carrier Card - PetaLinux 2018.2 Standard BSP
3.) created project: petalinux-create -t project –s
4.) copied xen-overlay.dtsi
Hi,
So, first of all:
1. use plaintext, not HTML
2. don't drop the xen-devel list (and other Cc-s) when replying.
:-)
That being said...
On Thu, 2018-09-13 at 09:38 +0200, Milan Boberic wrote:
> Hi Dario,
> yes passtrhough is involved.
>
Ok.
> This is everything I did so far:
>
> I impleme
On Wed, 2018-09-12 at 16:03 -0700, Stefano Stabellini wrote:
> Hi Dario,
>
> Milan has just found a bug in the null scheduler: apparently it is
> not
> possible to start a VM again after it has been destroyed.
>
> My initial suspicion was that the VM wasn't properly destroyed, but I
> asked Milan
Hi Dario,
Milan has just found a bug in the null scheduler: apparently it is not
possible to start a VM again after it has been destroyed.
My initial suspicion was that the VM wasn't properly destroyed, but I
asked Milan to double check with xl list, and the VM doesn't show in the
list anymore.
26 matches
Mail list logo
