Commit-ID: 3d6c50c27bd6418dceb51642540ecfcb8ca708c2
Gitweb: https://git.kernel.org/tip/3d6c50c27bd6418dceb51642540ecfcb8ca708c2
Author: Yun Wang
AuthorDate: Wed, 4 Jul 2018 11:27:27 +0800
Committer: Ingo Molnar
CommitDate: Wed, 25 Jul 2018 11:41:05 +0200
sched/debug: Show the sum wait
On Fri, Mar 27, 2015 at 6:49 PM, Jason Gunthorpe
wrote:
> On Fri, Mar 27, 2015 at 06:31:26PM +0100, Yun Wang wrote:
>
>> Maybe we can temporarily reserve the old logical, and gradually solve
>> these problems?
>
> It is best to make behavioral changes in small patches, yes
On Fri, Mar 27, 2015 at 6:16 PM, ira.weiny wrote:
> On Fri, Mar 27, 2015 at 10:13:19AM -0600, Jason Gunthorpe wrote:
>> On Fri, Mar 27, 2015 at 04:47:36PM +0100, Michael Wang wrote:
>> >
>> > Introduce helper has_iwarp() to help us check if an IB device
>> > support IWARP protocol.
>>
>> Should pr
On Fri, Mar 27, 2015 at 6:05 PM, ira.weiny wrote:
> On Fri, Mar 27, 2015 at 10:28:20AM -0600, Jason Gunthorpe wrote:
>> On Fri, Mar 27, 2015 at 04:46:57PM +0100, Michael Wang wrote:
>> >
[snip]
>> > -if (rdma_transport_is_ib(id_priv->cma_dev->device)) {
>> > +if (has_mcast(
On Fri, Mar 27, 2015 at 5:47 PM, ira.weiny wrote:
> On Fri, Mar 27, 2015 at 04:46:11PM +0100, Michael Wang wrote:
>>
>> Introduce helper has_sa() and cap_sa() to help us check if an IB device
>> or it's port support Subnet Administrator.
>
> I think these 2 should be combined. The question is if
Make sense to me if opa smi will be handled differently, will be
changed in next version :-)
Regards,
Michael Wang
On Fri, Mar 27, 2015 at 5:32 PM, Jason Gunthorpe
wrote:
> On Fri, Mar 27, 2015 at 04:44:43PM +0100, Michael Wang wrote:
>>
>> Introduce helper cap_smi() to help us check if the port
Time accounting for KVM guests running mixed IO and CPU workloads seems wrong.
KVM host: CentOS 6, x86_64, Linux 3.14.33
KVM guest: CentOS 6, x86_64, Linux 3.14.33, one vCPU.
Both guest and host enabled CONFIG_IRQ_TIME_ACCOUNTING and
CONFIG_PARAVIRT_TIME_ACCOUNTING
The KVM guest was running iper
Hi, folks
And this is my new mail address ;-)
Regards,
Michael Wang
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://ww
If this option is enabled, do we take VM steal time into account when
updating cpu_power?
As a result, there will be less load on vCPUs with smaller cpu_power ?
Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
On 08/11/2013 09:52 PM, Fengguang Wu wrote:
Alessandro,
FYI, the bug still exists in the upstream and linux-next kernels.
And it's caused by:
fc_probe(...) {
...
spin_lock(&fc_lock);
ret = misc_register(&fc->misc);
...
Hi, Miles
On 08/06/2013 12:30 PM, Miles Lane wrote:
I am not seeing any problems in the behavior of the computer, but
wonder if this indicates something that needs fixing.
[1.969109] WARNING: CPU: 1 PID: 1 at kernel/time/tick-sched.c:185
can_stop_full_tick+0x7e/0x89()
According to the com
11 matches
Mail list logo