From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH] KVM: Use thread debug register storage instead of kvm specific data Date: Tue, 01 Sep 2009 14:35:13 +0300 Message-ID: <4A9D06F1.3070900@redhat.com> References: <1251798248-13164-1-git-send-email-avi@redhat.com> <20090901112220.GA18271@amt.cnet> <4A9D056E.4030906@siemens.com> <20090901113225.GA18690@amt.cnet> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Jan Kiszka , "kvm@vger.kernel.org" To: Marcelo Tosatti Return-path: Received: from mx1.redhat.com ([209.132.183.28]:31795 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754143AbZIALfV (ORCPT ); Tue, 1 Sep 2009 07:35:21 -0400 In-Reply-To: <20090901113225.GA18690@amt.cnet> Sender: kvm-owner@vger.kernel.org List-ID: On 09/01/2009 02:32 PM, Marcelo Tosatti wrote: > >> Nope, kgdb writes directly to the debug registers. >> >> I vaguely recall someone trying to push a debug register management >> framework. Did it hit mainline in the meantime? I do not find any trace >> on quick glance, at least not in kgdb. >> > A simple kgdb_enabled sort of flag, in addition to TIF_DEBUG would do > it? > kgdb is per-cpu whereas user debugging is per-task, so we'd need a per-cpu debug register cache and flag. -- error compiling committee.c: too many arguments to function