From mboxrd@z Thu Jan  1 00:00:00 1970
From: Borislav Petkov <bp@alien8.de>
Subject: Re: [RFC PATCH] kvm: Make KVM DF intercept configurable
Date: Wed, 2 Mar 2016 10:07:42 +0100
Message-ID: <20160302090742.GA16954@pd.tnic>
References: <20160301192822.GD22677@pd.tnic>
 <56D6059D.5050606@redhat.com>
 <20160301224132.GE22677@pd.tnic>
 <56D68C21.7080602@siemens.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	=?utf-8?B?SsO2cmcgUsO2ZGVs?= <joro@8bytes.org>,
	Andy Lutomirski <luto@amacapital.net>, x86-ml <x86@kernel.org>,
	kvm ML <kvm@vger.kernel.org>,
	lkml <linux-kernel@vger.kernel.org>
To: Jan Kiszka <jan.kiszka@siemens.com>
Return-path: <linux-kernel-owner@vger.kernel.org>
Content-Disposition: inline
In-Reply-To: <56D68C21.7080602@siemens.com>
Sender: linux-kernel-owner@vger.kernel.org
List-Id: kvm.vger.kernel.org

On Wed, Mar 02, 2016 at 07:45:53AM +0100, Jan Kiszka wrote:
> To make this a serious debug feature, we should consider trapping all
> exceptions on request (and reinjecting the unhandled ones). Not sure
> right now, though, if that comes with more complications than the simple
> #DF case.

I can certainly try... Something like "intercept=<vector>,<vector>,..."
or so. Let me see how ugly it can get...

Thanks.

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.