Re: [Qemu-devel] [PATCH v2] rtc: placing RTC memory region outside BQL

> > > > > > > $ cat strace_c.sh > > > strace -tt -p $1 -c -o result_$1.log & > > > sleep $2 > > > pid=$(pidof strace) > > > kill $pid > > > cat result_$1.log > > > > > > Before appling this change: > > > $ ./strace_c.sh 10528 30 > > > % time seconds usecs/call callserrors syscall > >

Re: [Qemu-devel] [PATCH v2] rtc: placing RTC memory region outside BQL

> -Original Message- > From: Peter Maydell [mailto:peter.mayd...@linaro.org] > Sent: Tuesday, February 06, 2018 10:36 PM > To: Gonglei (Arei) > Cc: QEMU Developers; Paolo Bonzini; Huangweidong (C) > Subject: Re: [PATCH v2] rtc: placing RTC memory region outside BQL > > On 6 February 2018

Re: [Qemu-devel] [PATCH v2] rtc: placing RTC memory region outside BQL

On 6 February 2018 at 14:07, Gonglei wrote: > As windows guest use rtc as the clock source device, > and access rtc frequently. Let's move the rtc memory > region outside BQL to decrease overhead for windows guests. > Meanwhile, adding a new lock to avoid different vCPUs

[Qemu-devel] [PATCH v2] rtc: placing RTC memory region outside BQL

As windows guest use rtc as the clock source device, and access rtc frequently. Let's move the rtc memory region outside BQL to decrease overhead for windows guests. Meanwhile, adding a new lock to avoid different vCPUs access the RTC together. $ cat strace_c.sh strace -tt -p $1 -c -o