Sure. I actually think both should be deprecated, and replaced with
explicit "trace guest" vs "trace host" flags, just to make it
consistent, but I don't care deeply.
The only thing I care about is that compatibility must never be broken
(which the current setup does), and that people who don't use
virtualization should never be asked to use flags that have anything
to do with virtualization (which the current work-around involves).
Linus
On Sat, Dec 22, 2012 at 11:22 AM, David Ahern <dsah...@gmail.com> wrote:
> any opinions on whether the approach is reasonable?
>
> On 12/16/12 9:43 PM, David Ahern wrote:
>>
>> All that is needed is for the current exclude_guest flag to be
>> deprecated such that for older binaries on newer kernels it is ignored
>> (perhaps a warn on once), and then a new flag -- exclude_guest2 -- is
>> then used for the new logic.
--
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://www.tux.org/lkml/
