On Mon, Mar 12, 2012 at 3:32 PM, Alexander Graf wrote:
>
> On 08.03.2012, at 23:45, Christoffer Dall wrote:
>
>> Any comments on this one?
>
> While at it, how about you also add the PID? Otherwise it's pretty pointless
> to write information into the kernel log, as you still won't know which VM
On 08.03.2012, at 23:45, Christoffer Dall wrote:
> Any comments on this one?
While at it, how about you also add the PID? Otherwise it's pretty pointless to
write information into the kernel log, as you still won't know which VM it
origins from.
Also, I don't like the long function name. How
Any comments on this one?
On Thu, Feb 9, 2012 at 3:57 PM, Christoffer Dall
wrote:
> From: Christoffer Dall
>
> Introduces a couple of print functions, which are essentially wrappers
> around standard printk functions, with a KVM: prefix.
>
> Functions introduced or modified are:
> - kvm_err(fmt
From: Christoffer Dall
Introduces a couple of print functions, which are essentially wrappers
around standard printk functions, with a KVM: prefix.
Functions introduced or modified are:
- kvm_err(fmt, ...)
- kvm_info(fmt, ...)
- kvm_debug(fmt, ...)
- kvm_pr_unimpl(fmt, ...)
- pr_unimpl(vcpu
