[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH v1] domctl: hold domctl lock while domain is destroyed



I think it contend on page insertion into free pages list. But I don't confirm or denied this yet. I'm new in hypervisors...

11:19, 20 сентября 2021 г., Jan Beulich <jbeulich@xxxxxxxx>:

On 17.09.2021 18:01, Julien Grall wrote:

 I will quote what Hongyan wrote back on the first report:
 
 "
 The best solution is to make the heap scalable instead of a global
 lock, but that is not going to be trivial.
 
 Of course, another solution is to keep the domctl lock dropped in
 domain_kill() but have another domain_kill lock so that competing
 domain_kill()s will try to take that lock and back off with hypercall
 continuation. But this is kind of hacky (we introduce a lock to reduce
 spinlock contention elsewhere), which is probably not a solution but a
 workaround.
 "


Interesting. Is contention on the heap lock merely suspected or
was that lock proven to be the problem one?

Jan



--
Отправлено из мобильного приложения Яндекс.Почты

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.