Minor change in variable name and comments.
Signed-off-by: Meng Xu
[PATCH v1 1/3] xen:rtds: towards work conserving RTDS
[PATCH v1 2/3] libxl: enable per-VCPU extratime flag for RTDS
[PATCH v1 3/3] xl: enable per-VCPU extratime flag for RTDS
___
Xen-
On Sun, Aug 6, 2017 at 12:22 PM, Meng Xu wrote:
> Change main_sched_rtds and related output functions to support
> per-VCPU extratime flag.
>
> Signed-off-by: Meng Xu
>
> ---
> Changes from RFC v1
> Changes work_conserving flag to extratime flag
> ---
> tools/xl/x
On Mon, Aug 7, 2017 at 1:35 PM, Dario Faggioli
wrote:
> On Sat, 2017-08-05 at 17:35 -0400, Meng Xu wrote:
>> >
>> > > @@ -966,8 +1001,16 @@ burn_budget(const struct scheduler *ops,
>> > > struct
>> > > rt_vcpu *svc, s_time_t n
On Mon, Aug 7, 2017 at 3:14 PM, Dario Faggioli
wrote:
> On Mon, 2017-08-07 at 14:27 -0400, Meng Xu wrote:
>> On Mon, Aug 7, 2017 at 1:35 PM, Dario Faggioli
>>
>> > Is this wanted or expected?
>>
>> It is wanted.
>>
>> A VCPU i that has already go
On Tue, Aug 8, 2017 at 10:57 AM, Dario Faggioli
wrote:
> On Sun, 2017-08-06 at 12:22 -0400, Meng Xu wrote:
>> Make RTDS scheduler work conserving without breaking the real-time
>> guarantees.
>>
>> VCPU model:
>> Each real-time VCPU is extended to have an extra
On Tue, Aug 8, 2017 at 9:09 AM, Dario Faggioli
wrote:
> On Sun, 2017-08-06 at 22:43 -0400, Meng Xu wrote:
>> On Sun, Aug 6, 2017 at 12:22 PM, Meng Xu
>> wrote:
>> >
>> > diff --git a/tools/xl/xl_cmdtable.c b/tools/xl/xl_cmdtable.c
>> > index 2
On Tue, Aug 8, 2017 at 3:24 PM, Dario Faggioli
wrote:
> On Tue, 2017-08-08 at 12:16 -0700, Meng Xu wrote:
>> On Tue, Aug 8, 2017 at 9:09 AM, Dario Faggioli
>> wrote:
>> > On Sun, 2017-08-06 at 22:43 -0400, Meng Xu wrote:
>> > >
>> > > As to (1)
On Tue, Aug 8, 2017 at 3:52 PM, Dario Faggioli
wrote:
> On Tue, 2017-08-08 at 12:06 -0700, Meng Xu wrote:
>> On Tue, Aug 8, 2017 at 10:57 AM, Dario Faggioli
>> wrote:
>> > On Sun, 2017-08-06 at 12:22 -0400, Meng Xu wrote:
>> > >
>> > > diff
On Wed, Aug 9, 2017 at 3:32 AM, Dario Faggioli
wrote:
> On Tue, 2017-08-08 at 15:55 -0700, Meng Xu wrote:
>> On Tue, Aug 8, 2017 at 3:24 PM, Dario Faggioli
>> wrote:
>> >
>> > Therefore, I think I would set extratime as on by default in both
>&
On Mon, Jul 3, 2017 at 7:03 AM, Andrii Anisov wrote:
>
> Dear Meng Xu,
Hi Andrii,
>
>
> We are going to evaluate an RTDS scheduler on ARM.
>
>
> Basically I'm going to repeat use-cases described in
> https://www.cis.upenn.edu/~linhphan/papers/emsoft14-rt-xen.pdf
ady.
>
> Signed-off-by: Haoran Li
> Reviewed-by: Meng Xu
As Dario mentioned in the email, the title should be changed and the
email should be a new email thread, instead of a forward email.
A reference to the format of sending a newer version of patch can be
found at https://www.m
On Mon, Jul 3, 2017 at 10:58 AM, Andrii Anisov wrote:
> Hello Meng Xu,
>
>
> On 03.07.17 16:35, Meng Xu wrote:
>>>
>>> Do you have any recommendations or suggestions?
>>
>> Which experiment/use case do you plan to run?
>> What are the requireme
On Tue, Jul 4, 2017 at 8:28 AM, Andrii Anisov wrote:
>
>
> On 03.07.17 21:42, Meng Xu wrote:
>>
>> As far as I know, there is no known issue for ARM as long as that
>> version Xen runs on the ARM board.
>
> That's good.
>>
>> I assume you have
indexed by COS ID.
> +
> + - Member `dom_ids`
> +
> +`dom_ids` is a bitmap, every bit corresponds to a domain. Index is
> + domain_id. It is used to help restore domain_id to 0 when a socket is
> +offline and then online ag
On Wed, Jul 5, 2017 at 4:29 AM, Dario Faggioli
wrote:
> On Tue, 2017-07-04 at 11:12 -0400, Meng Xu wrote:
>> On Tue, Jul 4, 2017 at 8:28 AM, Andrii Anisov > > wrote:
>> >
>> > So you are suggesting to introduce more RT schedulers with
>> > different algo
On Wed, Jul 5, 2017 at 4:51 AM, Dario Faggioli
wrote:
> On Mon, 2017-07-03 at 14:42 -0400, Meng Xu wrote:
>> On Mon, Jul 3, 2017 at 10:58 AM, Andrii Anisov > m> wrote:
>> >
>> Once the scheduling policy is determined, you will need to configure
>> the VC
t to argue about the real-time timing properties required
by some safety-critical systems' standard, such as the ISO-26262 for
automotive systems, the system support (such as the RTDS scheduler),
the correct configuration of the system, and the analysis computation
and analysis will be required
On Mon, Jul 10, 2017 at 1:25 AM, Yi Sun wrote:
> On 17-07-07 12:37:28, Meng Xu wrote:
>> > + Sample cache capacity bitmasks for a bitlength of 8 are shown below.
>> > Please
>> > + note that all (and only) contiguous '1' combinations are allowed (e.g
type,
> - make x86's paging_domctl() and descendants take a properly typed
> handle,
> - add const in a few places.
>
> Signed-off-by: Jan Beulich
Acked-by: Meng Xu
Thanks,
Meng
--
Meng Xu
Ph.D. Candidate in Computer and Information Science
University of Penn
Hi Dario,
On Wed, Sep 13, 2017 at 9:06 PM, Dario Faggioli
wrote:
>
> On Fri, 2017-09-01 at 11:58 -0400, Meng Xu wrote:
> > Make RTDS scheduler work conserving without breaking the real-time
> > guarantees.
> >
> > VCPU model:
> > Each real-time VCPU is extend
On Wed, Sep 13, 2017 at 8:16 PM, Dario Faggioli
wrote:
> On Fri, 2017-09-01 at 12:03 -0400, Meng Xu wrote:
>> On Fri, Sep 1, 2017 at 11:58 AM, Meng Xu
>> wrote:
>> > @@ -705,6 +717,12 @@ static int sched_rtds_domain_set(libxl__gc
>> > *gc, uint32_t domid,
&
Hi Andrii,
On Wed, Sep 27, 2017 at 8:37 AM, Andrii Anisov wrote:
>
> Dear Meng Xu,
>
>
> On 22.08.17 05:02, Meng Xu wrote:
>>
>> Given the set of tasks in each VM, we compute the VCPUs' periods and
>> budgets, using the CARTS tool [1]. Note that each
On Wed, Sep 27, 2017 at 10:37 AM, Andrii Anisov wrote:
> Hello,
>
>
> On 27.09.17 16:57, Meng Xu wrote:
>>
>> The command is:
>> java -jar carts.jar inputfile outputfile
>
> From the next example, I would say the command is:
> java -jar carts.jar inpu
On Mon, Oct 2, 2017 at 1:04 PM, Dario Faggioli
wrote:
> On Mon, 2017-10-02 at 17:38 +0300, Andrii Anisov wrote:
> > Hello Meng Xu and Dario,
> >
> Hi,
>
> > On 01.09.17 18:58, Meng Xu wrote:
> > > This series of patches make RTDS scheduler work-conserv
Hi Jan and Boris,
I'm Meng Xu from the University of Pennsylvania.
I'm wondering:
How does Xen (vpmu) handle the general performance counter's overflow interrupt?
Could you point me to the function handler, if Xen does handle it?
---What I want to achieve---
I'm look
[Sorry, I cc.ed Quan's previous email at Intel. Change to his current email.]
On Fri, Mar 31, 2017 at 11:41 AM, Meng Xu wrote:
> Hi Jan and Boris,
>
> I'm Meng Xu from the University of Pennsylvania.
>
> I'm wondering:
> How does Xen (vpmu) handle the gener
tried to set MSR_CORE_PERF_GLOBAL_OVF_CTRL to 0xf, but the
register's content is not changed. :(
Maybe I should set the MSR_CORE_PERF_GLOBAL_OVF_CTRL to 0xF to enable
the overflow interrupt?
Thank you very much for your time and help!
Meng
---
Meng Xu
PhD Candidate in Computer and Information Science
U
little executable, that users could use
> to find out whether their ram is vulnerable? That would be extremely
> valuable.
Google does have a github repo to do the rowhammer test:
https://github.com/google/rowhammer-test
Meng
---
Meng Xu
PhD Student in Computer and Information Scie
he chapter for the L2 CAT and the version of
the SDM you are referring?
It makes people's life easier to find the reference. ;-)
>
> # History
>
>
> Date Revision Version Notes
> -- ---
> 2016-08-12 1.0 Xen 4.7 Initial design
It seems there is a RFC design in May this year:
http://www.gossamer-threads.com/lists/xen/devel/431142
Shouldn't it be counted?
Thanks,
Meng
---
Meng Xu
PhD Student in Computer and Information Science
University of Pennsylvania
http://www.cis.upenn.edu/~mengxu/
___
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
On Sat, Sep 17, 2016 at 10:34 PM, Yi Sun wrote:
> On 16-09-17 11:31:54, Meng Xu wrote:
>> On Thu, Aug 25, 2016 at 1:21 AM, Yi Sun wrote:
>> >
>> > Design document is below:
>> > ===
>>
cpumask_test_cpu(new->vcpu->processor, ¬_tickled))
You should have a space before the last ).
Can you resend the patch with the comment resolved?
Thanks,
Meng
--
Meng Xu
PhD Student in Computer and Information Science
University of Pennsylvania
http://www.cis.upenn.edu/~mengxu/
___
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
tel.com/content/www/us/en/processors/architectures-software-developer-manuals.html)
> +
I checked the document. The CAT is in Chapter 17.17. However, there is
no description about the MBA? ;-)
Thanks,
Meng
---
Meng Xu
PhD Student in Computer and Information Science
University of Pennsylvania
http://www.cis.upenn.edu/~mengxu/
___
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
now. I guess I downloaded the old version. :-)
I found this MBA feature is interesting. Is there any processor on the
market we can purchase?
We'd like to evaluate this feature. ;-)
Thanks,
Meng
---
Meng Xu
PhD Student in Computer and Information Science
University of Pennsylvania
http://www.cis.upenn.edu/~mengxu/
___
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
cpumask_clear_cpu(cpu, ¬_tickled);
> +cpu = cpumask_cycle(cpu, ¬_tickled);
> }
>
> -/* 3) candicate has higher priority, kick out lowest priority vcpu */
> +/* 2) candicate has higher priority, kick out lowest priority vcpu */
> if (
> automatically take all knowledge the scheduler has into account.
>
> Signed-off-by: George Dunlap
> ---
> CC: Dario Faggioli
> CC: Anshul Makkar
> CC: Meng Xu
> CC: Jan Beulich
> ---
> xen/common/sched_credit.c | 3 +++
> xen/common/sched_credit2.c | 12 +++
gt;>> runqueue load, as in credit2).
>>>
>>> To solve this, when inserting a vcpu, always call the per-scheduler
>>> "pick" function to revise the initial placement. This will
>>> automatically take all knowledge the scheduler has into account.
&
- Actually grab lock before calling vcpu_schedule_lock() to avoid
> tripping over a new ASSERT
>
> CC: Dario Faggioli
> CC: Anshul Makkar
> CC: Meng Xu
> CC: Jan Beulich
> ---
> xen/common/sched_credit.c | 3 +++
> xen/common/sched_credit2.c | 11 ++-
> x
) Scheduling point
a) VCPU’s budget is depleted for the current priority index
b) VCPU starts a new period
c) VCPU is blocked or waked up
3) Scheduling decision is made when scheduler is invoked
a) Always pick the current M highest-priority VCPUs to run on the M cores.
---
Meng
On Mon, Aug 8, 2016 at 5:38 AM, Dario Faggioli
wrote:
> On Thu, 2016-08-04 at 01:15 -0400, Meng Xu wrote:
>> Hi Dario,
>>
> Hi,
>
>> I'm thinking about changing the current RTDS scheduler to
>> work-conserving version as we briefly discussed before.
>&
/
>>> /Shell
>>>
>>> /
>>> I am following this wiki (http://wiki.xen.org/wiki/HiKey) to
>>> setup xen in hikey. I am not sure what could cause this issue
>>> here. Appreciate all of you input and a
e cpu that is going through the scheduler has
> been tickled or not, if it is currently idle, etc
> (they vary, on a per-scheduler basis).
>
> For Credit1 and Credit2, add a record about when
> rate-limiting kicks in too.
>
> Signed-off-by: Dario Faggioli
> ---
> Cc: Georg
On Thu, Aug 18, 2016 at 6:22 AM, Dario Faggioli
wrote:
> On Tue, 2016-08-09 at 09:57 -0400, Meng Xu wrote:
>> On Mon, Aug 8, 2016 at 5:38 AM, Dario Faggioli
>> wrote:
>> >
>> > I'm just thinking out loud and
>> > wondering:
>> > - could
EN) d0v2: vGICD: unhandled word write 0x to ICACTIVER0
>> > (XEN) d0v3: vGICD: unhandled word write 0x to ICACTIVER0
>> >
>> > It just hang there after the last line above.
>> > I have looked into those messages " d0v3: vGI
2144 (~100%)
>
> Stop printing details of idle vCPUs also in Credit1
> and RTDS (they're pretty useless in there too).
>
> Signed-off-by: Dario Faggioli
> ---
> Cc: George Dunlap
> Cc: Anshul Makkar
> Cc: Meng Xu
> ---
> xen/common/sched_credit.c |6 ++--
On Thu, Jan 26, 2017 at 5:08 PM, Dario Faggioli
wrote:
> On Thu, 2017-01-26 at 13:59 -0500, Meng Xu wrote:
>> Hi Dario,
>>
> Hi,
>
>> On Thu, Jan 26, 2017 at 11:52 AM, Dario Faggioli
>> wrote:
>> >
>> > Runqueue 0:
>> > CPU[0
27;t remember).
> > >
> > > That being said, it's not that I can't live with the added "idle"
> > > indication. But I like it less and would prefer not to add it.
> >
> > Sure! I was thinking if we should even avoid printing out the idle
>
ore=,00ff
> RUNQ:
> 0: [0.1] flags=0 cpu=2 credit=6561215 [w=256] load=262144 (~100%)
> 1: [0.2] flags=0 cpu=2 credit=5812356 [w=256] load=262144 (~100%)
>
> Stop printing details of idle vCPUs also in Credit1
> and RTDS (they're pretty useless in
ybe
he has a repo. for the kernel.
Meng
---
Meng Xu
PhD Student in Computer and Information Science
University of Pennsylvania
http://www.cis.upenn.edu/~mengxu/
___
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
ock source TSC with a granularity of
> nanoseconds. I'd like to know if there is any reason that the Xen hypervisor
> does not choose a nanosecond scheduler?
What do you mean by a nanosecond scheduler? In the kernel, scheduler
accounts the budget in nanoseconds.
Meng
--
in burn_budget function in sched_rt.c .
>
> Again, thanks a lot for your help.
:-)
Meng
>
>
> Quoting Meng Xu :
>
>> [cc. Dario and George]
>>
>> On Fri, Jan 6, 2017 at 1:34 PM, wy11 wrote:
>>>
>>> Dear Xen developers,
>>
>>
>> Hi,
&
pu that is going through the scheduler has
> been tickled or not, if it is currently idle, etc
> (they vary, on a per-scheduler basis).
>
> For Credit1 and Credit2, add a record about when
> rate-limiting kicks in too.
>
> Signed-off-by: Dario Faggioli
> ---
> Cc: George Dunl
pu that is going through the scheduler has
> been tickled or not, if it is currently idle, etc
> (they vary, on a per-scheduler basis).
>
> For Credit1 and Credit2, add a record about when
> rate-limiting kicks in too.
>
> Signed-off-by: Dario Faggioli
> ---
> Cc: George Dunl
On Tue, Oct 18, 2016 at 6:51 AM, Wei Liu wrote:
> CC Dario and Meng
Thank you very much for cc.ing me, Wei! :-)
>
> On Mon, Oct 17, 2016 at 10:55:21PM +0100, Juergen Schinker wrote:
>> Hey Meng XU
Hi,
Thanks for your interest in RTDS scheduler! :-)
>>
>>
>>
e verified.
> +
> +Finally, to check that the scheduler is working properly (although only
> +at a macroscopic level), the following should be done:
> +
> +* create a VM with 1 vCPU and put it in the RTDS cpupool,
> +* set the scheduling parameters such as it has a 50% reservation
Correct the mistakes in the example command
Correct a simple typo.
Signed-off-by: Meng Xu
---
Cc: Meng Xu
Cc: Dario Faggioli
Cc: Wei Liu
Cc: Lars Kurth
Cc: George Dunlap
Cc: Chong Li
---
docs/features/sched_rtds.pandoc | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff
context switching
out,
we will always tickle the core where the VCPU was running,
if the VCPU cannot find another core to tickle
This bug was reported by Dagaen Golomb
Signed-off-by: Meng Xu
---
Cc: Dagaen Golomb
Cc: Dario Faggioli
Cc: George Dunlap
Cc: Wei Liu
Cc: Linh Thi Xuan Phan
On Wed, Oct 19, 2016 at 11:13 AM, Meng Xu wrote:
> The bug is introduced in Xen 4.7 when we converted RTDS scheduler
> from quantum-driven model to event-driven model.
> We assumed rt_schedule() is always called for a VCPU
> before the VCPUs budget replenished handler.
> This assu
[cc. Tianyang...]
On Wed, Oct 19, 2016 at 11:45 AM, Wei Liu wrote:
> On Wed, Oct 19, 2016 at 11:13:54AM -0400, Meng Xu wrote:
>> The bug is introduced in Xen 4.7 when we converted RTDS scheduler
>> from quantum-driven model to event-driven model.
>> We assumed rt_schedule()
On Fri, Oct 21, 2016 at 1:36 PM, Dario Faggioli
wrote:
>
> On Wed, 2016-10-19 at 11:13 -0400, Meng Xu wrote:
> > The bug is introduced in Xen 4.7 when we converted RTDS scheduler
> > from quantum-driven model to event-driven model.
> > We assumed rt_schedule() is
We should clear the __RTDS_depleted bit once a VCPU budget is replenished.
Because repl_timer_handler may be called after rt_schedule
but before rt_context_saved, the VCPU may be not on CPU or on queue
when the VCPU is the middle of context switch
Signed-off-by: Meng Xu
---
Cc: Dario Faggioli
.
Fix:
We keeps last_start always within the current period for a VCPU, so that
We only deduct the time spent in the current period from the VCPU budget.
Signed-off-by: Meng Xu
Reported-by: Dagaen Golomb
---
Cc: Dario Faggioli
Cc: George Dunlap
Cc: Wei Liu
Cc: Linh Thi Xuan Phan
Cc: Haoran Li
On Fri, Oct 21, 2016 at 10:11 PM, Meng Xu wrote:
> Bug scenario:
> While a VCPU is running on a core, it may misses its deadline.
> Then repl_timer_handler() will update the VCPU period and deadline.
> The VCPU may have high priority with the new deadline and repl_timer_handler()
On Tue, Oct 25, 2016 at 5:20 AM, Dario Faggioli
wrote:
> On Fri, 2016-10-21 at 22:12 -0400, Meng Xu wrote:
>> We should clear the __RTDS_depleted bit once a VCPU budget is
>> replenished.
>> Because repl_timer_handler may be called after rt_schedule
>> but before rt_con
On Wed, Oct 26, 2016 at 10:43 AM, Dario Faggioli
wrote:
> On Fri, 2016-10-21 at 22:11 -0400, Meng Xu wrote:
>> Bug scenario:
>> While a VCPU is running on a core, it may misses its deadline.
>>
> May be useful to mention why (at least the most common reasons, like
> o
>
>> Since we always account for the time spent in hypervisor into the
>> budget of currently running VCPU, I chose last_start = cur_deadline -
>> period.
>> I'm ok for last_start = now, considering the consistency. So your
>> call. :-)
>>
> I
.
Signed-off-by: Meng Xu
Reported-by: Dagaen Golomb
---
Cc: Dario Faggioli
Cc: George Dunlap
Cc: Wei Liu
Cc: Linh Thi Xuan Phan
Cc: Haoran Li
Cc: Meng Xu
Cc: Dagaen Golomb
Cc: Tianyang Chen
---
Changes from v1:
* Change commit message to make the bug scenario easier to understand;
* The
We keep last_start updated whenever cur_budget is updated.
This avoids subtle bugs in case burn_budget() will be called
in other places in the future.
Signed-off-by: Meng Xu
---
Cc: Dario Faggioli
Cc: George Dunlap
Cc: Wei Liu
Cc: Linh Thi Xuan Phan
Cc: Haoran Li
Cc: Meng Xu
Cc: Dagaen
Hi Wei and Dario,
On Thu, Oct 27, 2016 at 6:03 AM, Wei Liu wrote:
> On Thu, Oct 27, 2016 at 11:14:36AM +0200, Dario Faggioli wrote:
>> On Wed, 2016-10-26 at 15:06 -0400, Meng Xu wrote:
>> > We keep last_start updated whenever cur_budget is updated.
>> > This
Sorry, I accidentally sent out the previous email...
On Thu, Oct 27, 2016 at 6:03 AM, Wei Liu wrote:
> On Thu, Oct 27, 2016 at 11:14:36AM +0200, Dario Faggioli wrote:
>> On Wed, 2016-10-26 at 15:06 -0400, Meng Xu wrote:
>> > We keep last_start updated whenever cur_budget is
"QEMU xen-blkback performance analysis and
> improvements", as shown in
> https://wiki.xenproject.org/wiki/Outreach_Program_Projects.
You can use to highlight the sentence.
People use the plain text in the ML. :-)
Meng
--
---
Meng Xu
PhD Student in Computer and
beyond
> +
I'm interested in trying out your code.
I'm planning to purchase a SoC with the Atom Goldmont processors.
Do you have some suggestions about the SoC I should purchase?
I would prefer to use the same
I'm at EST (GMT-5).
Thank you very much!
Meng
---
Meng Xu
PhD Student in Computer and Information Science
University of Pennsylvania
http://www.cis.upenn.edu/~mengxu/
___
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
Hi Dario,
Thank you very much for the explanation! I got it. To be specific,
2015-11-04 10:52 GMT-05:00 Dario Faggioli :
> On Wed, 2015-11-04 at 10:01 -0500, Meng Xu wrote:
> > 2015-11-04 9:12 GMT-05:00 Dario Faggioli :
> > > Just FTR (and for next time :-D), is the above
roject.org/archives/html/xen-devel/2015-03/msg01219.html
Best,
Meng
-------
Meng Xu
PhD Student in Computer and Information Science
University of Pennsylvania
http://www.cis.upenn.edu/~mengxu/
___
Xen-devel mailing list
Xen-devel@lists.xe
HI Edgar,
Thank you so much for your reply!
2015-11-06 13:25 GMT-05:00 Edgar E. Iglesias :
> On Fri, Nov 06, 2015 at 01:19:04PM -0500, Meng Xu wrote:
> > Hi,
>
> Hi Meng,
>
> >
> > I saw Xen is supported on Xilinx ZynqMP platform at [1].
> > I want to hav
115200n8 earlyprintk=xen
quiet splash
echo'Loading initial ramdisk ...'
module /boot/initrd.img-3.8.0-44-generic
}
[1] http://wiki.xenproject.org/wiki/Xen_Serial_Console
--
---
Meng Xu
PhD Student in Computer and Information Science
University of Pennsylvania
h
/boot/vmlinuz-3.8.0-44-generic placeholder root=/dev/sda5
> ro panic=10 panic_on_oops=1 console=hvc0,115200n8 earlyprintk=xen
> quiet splash
>
> echo'Loading initial ramdisk ...'
>
> module /boot/initrd.img-3.8.0-44-generic
>
> }
>
>
Finally,
command line works:
placeholder dom0_mem=8192M,max:8192M dom0_max_vcpus=8 sched=credit
com1=115200,8n1,pci console=com1,vga
Thank you again for your help!
Best regards,
Meng
--
---
Meng Xu
PhD Student in Computer and Information Science
University of Pennsylvania
http://www.cis.upenn.edu/~meng
***
(XEN)
(XEN) Reboot in five seconds...
***It says "Reboot in five seconds", but I want for 1 min and nothing
happened. :-(
Did anyone happen to know why Xen does not reboot under this situation?
(Xen could reboot if it fails on an ASSERT())
Thank you very much for your time and h
Hi Andrew,
First, thank you so much for your super fast reply! I really appreciate it. :-)
2015-11-11 17:54 GMT-05:00 Andrew Cooper :
> On 11/11/2015 22:49, Meng Xu wrote:
>> Hi all,
>>
>> I'm trying to work remotely with the machine I have. So I want Xen
>
Hi Andrew,
2015-11-11 18:34 GMT-05:00 Andrew Cooper :
> On 11/11/2015 23:21, Meng Xu wrote:
>>
>>> Finally, I can't tell from your paste below, but ensure that you are
>>> always using a debug hypervisor.
>> The source file Config.mk under the xen folder has
Hi Andrew,
2015-11-12 7:52 GMT-05:00 Andrew Cooper :
> On 12/11/15 02:10, Meng Xu wrote:
>> Hi Andrew,
>>
>> 2015-11-11 18:34 GMT-05:00 Andrew Cooper :
>>> On 11/11/2015 23:21, Meng Xu wrote:
>>>>> Finally, I can't tell from your paste below,
put some printk in the machine_restart as Andrew suggested to
see if I can find more information. If you happen to know any other
ways that I can try, could you let me know?
Thank you very much!
Best,
Meng
---
Meng Xu
PhD Student in Computer and Information Science
University o
ggestions?
Thank you very much for your help!
Best,
Meng
---
Meng Xu
PhD Student in Computer and Information Science
University of Pennsylvania
http://www.cis.upenn.edu/~mengxu/
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
I think the machine_restart() may have a bug. :-(
2015-11-12 11:13 GMT-05:00 Meng Xu :
> Hi Andrew,
>
> I thought I might find where the system got stuck.
>
> As you suggested, I add several printks inside machine_restart();
> If the machine restart when Xen kernel cras
();
__stop_this_cpu();
disable_IO_APIC();
hpet_disable();
local_irq_enable();
I'm guessing at __stop_this_cpu() when it is on P0, P0 will be
stopped. That's why P0 will never have the chance to proceed to the
rest of logic in th
think this could be a fix?
>
> Definitely not.
I see the reason now...
This issue does not happen on another machine of mine. Probably it is
because of the oddity on the assembled machine, as Jan said. :-(
Thank you very much for your help and advice!
Best,
Meng
--
---
Meng Xu
PhD Student in Computer and Information Science
University of Pennsylvania
http://www.cis.upenn.edu/~mengxu/
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
tion*/
> ret.task = snext->vcpu;
>
Tianyang,
The comment for this line should not be changed. The new comment
should be in the commit message since this is the explanation of the
whole patch.
Thanks,
Meng
---
Meng Xu
PhD Student in Computer and
Hi Dario,
2015-11-19 4:51 GMT-05:00 Dario Faggioli :
> Hi,
>
> Thanks Tianyang for the report and for the patch, and Meng for helping
> getting the patch itself on the list and to me, and for commenting.
>
> On Wed, 2015-11-18 at 22:38 -0500, Meng Xu wrote:
>> [cc. Dario
> The experiment I am doing is running real time tasks with different total
> utilization rate and measure the task success rate in the vm.
Which kind of RT tasks are you running inside VM? Are they
independent? Are they involving a lot of I/O or memory?
Thanks,
Meng
>
>
Hi,
2015-11-23 11:35 GMT-05:00 Yu-An(Victor) Chen :
> Hi Meng,
>
> Thank you very much for replying!
>
> The RT tasks I am running for each trial at a certain utilization rate is a
> collection of real-time tasks, and each real-time task is a sequence of jobs
> that are released periodically. All
ast, make sure
it has no problem in applying on the latest commit point.
>>
>> What are the rules again, then? Dario is a scheduler maintainer, and
>> Meng is an established contributor. I thought that was enough.
>
> My understanding is that patches by maintainers need
does, the IPI issue may still exist
in LITMUS. :-( Then you have to look at the TRACE to figure out which
part misses the IPI in LITMUS.
>
> Again, thank you very much, I really appreciate your help!
No problem.
Meng
>
> Victor
>
>
>
>
>
>
> On Mon, Nov 23, 2015 at 6
2015-11-27 12:23 GMT-05:00 Dario Faggioli :
> On Fri, 2015-11-27 at 08:36 -0800, Yu-An(Victor) Chen wrote:
>> Hi Dario,
>>
> Hi,
>
>> Thanks for the reply!
>>
> You're welcome. :-)
>
> I'm adding Meng to Cc...
>
Thanks! :-)
>> My goal for the experiment is to show that xen rtds scheduler is
>> be
When a taskset
miss ddl., which task inside miss deadline?
Meng
>
> Thank you both very much again, if there is any unclear part, please lemme
> know, thx!
>
> Victor
>
>
>
> On Fri, Nov 27, 2015 at 9:41 AM, Meng Xu wrote:
>>
>> 2015-11-27 12:23 GMT-05:00 D
taks utilization in a taskset,
scheduling algorithm, task period relation, can affect schedulability
also.
Best,
Meng
>
>
> On Fri, Nov 27, 2015 at 4:17 PM, Meng Xu wrote:
>>
>> 2015-11-27 14:50 GMT-05:00 Yu-An(Victor) Chen :
>> > Hi Dario & Meng,
>> >
&
nto the reference you provide, I just started my research
> in the rt fields, there is still a lot for me to learn. Thank you again for
> reply!
>
Yeah, you need to read and learn the real-time scheduling theory,
especially you are doing research in RT field. :-D
>
> Thank you!
&
completion time of the job is 79ms and then 87ms, and then 95ms
> >
> That depends on how missing a deadline is handled and accounted for. I
> don't recall how Litmus^RT does that.
LITMUS by default let the task keep running even when it misses deadline.
But if users speci
2015-11-29 11:27 GMT-05:00 Dario Faggioli :
> On Sun, 2015-11-29 at 10:38 -0500, Meng Xu wrote:
>>
>>
>> 2015-11-29 7:46 GMT-05:00 Yu-An(Victor) Chen :
>> > Hi Meng,
>> >
>> Hi,
>>
>> >
>> > So I will rewrite my setup here again,
Hi Wei,
>
>
> * Improve RTDS scheduler (none)
It has two parts:
>
>Change RTDS from quantum driven to event driven
This is part 1 which only involves the hypervisor change;
The part 2 is supporting per-vcpu parameter get/set function in the toolstack.
>
> - D
101 - 200 of 397 matches
Mail list logo
