[PATCH 3/3] nvme: add KConfig options for debug features

[Chaitanya Kulkarni]

>>>> A controller(s) that is used in the production environment goes
>>>> through qualification process from vendors and from the consumers
>>>> to make sure they are stable, something like spurious completions
>>>> detection is a basic part of the qualification,
>>>
>>> I don't think that assuming that a production controller does not
>>> have any hidden bugs is a great practice, and controllers evolve during
>>> their production lifetime.
>>>
>>
>> That is why we should keep it configurable and let user decide.
> 
> OK, so this allows a user that is absolutely set on shaving few
> nano-seconds to sacrifice a level of protection against buggy
> controllers. Is this a real use-case?
> 
> For that, I guess the config option is fine, but this at the very least
> needs to default to y.

Okay, I'll send out V2 with default options set to y.