r.dtsi
file.
Thank you in adance, best regards, Milan Boberic.
name = "bm1"
kernel = "ultraled.bin"
memory = 8
vcpus = 1
cpus = [2]
irqs = [ 48 ]
iomem = [ "0xff0a0,1" ]
hap=0[0.00] Booting Linux on physical CPU 0x0
[0.00] Linux version 4.14.0-xilinx-v201
tion of that bm app and then run xl create it will create it
without error.
This is github repository of Xen I use:
https://github.com/Xilinx/xen/tree/xilinx/stable-4.10
Is there anything else I can send that would be helpful?
Thanks in advance, best regards, Milan Boberic.
On Thu, Sep 13, 2018
end you back the results.
In attachment I included dmesg, xl dmesg from xen 4.10.
On Thu, Sep 13, 2018 at 7:39 PM Dario Faggioli wrote:
>
> 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
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
0042:End of a domain_destroy function
(XEN) t=339215321153:End of a complete_domain_destroy function
Also thank you for taking your time to help me, best regards!
On Thu, Sep 20, 2018 at 6:09 PM Dario Faggioli wrote:
>
> Hey,
>
> Sorry for not having followed up. I was (and still am) planning to, but
&
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
ill I get any performance improvement,
I will remove them right away.
Best regards, Milan Boberic!
On Tue, Sep 25, 2018 at 1:15 PM Julien Grall wrote:
>
> Hi Dario,
>
> On 09/25/2018 10:02 AM, Dario Faggioli wrote:
> > On Mon, 2018-09-24 at 22:46 +0100, Julien Grall 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 your opinions)?
And what this patch exactly do? I need to fully underst
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,
> > the
> > various phy
anks in advance, Milan Boberic.
___
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
arget list (0x2). Skip it
(XEN) d2v0 No valid vCPU found for vIRQ41 in the target list (0x2). Skip it
In attachments I included dmesg, xl dmesg and bare-metal application's
configuration file.
Thanks in advance, Milan Boberic.
On Tue, Oct 9, 2018 at 6:46 PM Dario Faggioli wrote:
>
&g
Attachments.
name = "test"
kernel = "timer.bin"
memory = 8
vcpus = 1
cpus = [1]
irqs = [ 48, 54, 68, 69, 70, 71, 72, 73, 74, 75, 76, 77, 78, 79 ]
iomem = [ "0xff010,1", "0xff110,1", "0xff120,1", "0xff130,1", "0xff140,1",
"0xff0a0,1" ][0.00] Booting Linux on physical CPU 0x0
[0.00]
configuration file. It would be helpful to know if those
setting are correct. If they are not correct it would explain the
jitter.
Thanks in advance, Milan Boberic!
/ {
chosen {
#address-cells = <2>;
#size-cells = <1>;
xen,xe
I misunderstood the passthrough concept, it only allows guest domain
to use certain interrupts and memory. Is there are way to somehow
route interrupt from domU (bare-metal app) to hw?
On Thu, Oct 11, 2018 at 9:36 AM Milan Boberic wrote:
>
> On Wed, Oct 10, 2018 at 6:41 PM Meng Xu
efano Stabellini <
stefano.stabell...@xilinx.com> wrote:
> On Thu, 11 Oct 2018, Milan Boberic wrote:
> > On Wed, Oct 10, 2018 at 6:41 PM Meng Xu wrote:
> > >
> > > The jitter may come from Xen or the OS in dom0.
> > > It will be useful to know what is the
Hi,
> Don't interrupt _come_ from hardware and go/are routed to
> hypervisor/os/app?
Yes they do, sorry, I reversed the order because I'm a newbie :) .
> Would you mind to explain what is the triple timer counter?
On this link on page 342 is explanation.
> This is not the official Xen repository
> On 15/10/2018 09:14, Julien Grall wrote:
> Which link?
I made hyperlink on "link" word, looks like somehow it got lost, here
is the link:
https://www.xilinx.com/support/documentation/user_guides/ug1085-zynq-ultrascale-trm.pdf
> The board should be fully supported upstreamed. If Xilinx has more
Hi,
>
> The device tree with everything seems to be system.dts, that was enough
> :-) I don't need the dtsi files you used to build the final dts, I only
> need the one you use in uboot and for your guest.
I wasn't sure so I sent everything, sorry for being bombarded with
all those files. :-)
>
Hi,
> I think we want to fully understand how many other interrupts the
> baremetal guest is receiving. To do that, we can modify my previous
> patch to suppress any debug messages for virq=68. That way, we should
> only see the other interrupts. Ideally there would be none.
> diff --git a/xen/arc
> Just add an && irq != 1023 to the if check.
Added it and now when I create bare-metal guest it prints only once:
(XEN) DEBUG irq=0
(XEN) d1v0 No valid vCPU found for vIRQ32 in the target list (0x2). Skip it
(XEN) d1v0 No valid vCPU found for vIRQ33 in the target list (0x2). Skip it
(XEN) d1v0 No
Hi,
> On Wed, Oct 24, 2018 at 2:24 AM Stefano Stabellini
> wrote:
> It is good that there are no physical interrupts interrupting the cpu.
> serrors=panic makes the context switch faster. I guess there are not
> enough context switches to make a measurable difference.
Yes, when I did:
grep ctxt
On Thu, Oct 25, 2018 at 1:30 PM Julien Grall wrote:
>
> Hi Milan,
Hi Julien,
> Sorry if it was already asked. Can you provide your .config for your
> test?
Yes of course, bare-metal's .cfg file is in it's in attachment (if
that is what you asked :) ).
> Do you have DEBUG enabled?
I'm not sur
> I was asking the Xen configuration (xen/.config) to know what you have
> enabled in Xen.
Oh, sorry, because I'm building xen from git repository here is the
link to it where you can check the file you mentioned.
https://github.com/Xilinx/xen/tree/xilinx/versal/xen
> It might, OTOH, be wise to
Sorry for late reply,
> I am afraid no. .config is generated during building time. So can you
> paste here please.
".config" file is in attachment.
I also tried Xen 4.9 and I got almost same numbers, jitter is smaller
by 150ns which isn't significant change at all.
Milan
#
# Automatically gene
Hi,
> Interesting. Could you confirm the commit you were using (or the point
> release)?
> Stefano's number were based on commit "fuzz: update README.afl example"
> 55a04feaa1f8ab6ef7d723fbb1d39c6b96ad184a which is an unreleased version
> of Xen.
All Xens I used are from Xilinx git repository bec
25 matches
Mail list logo
