On Thu, Feb 23, 2023 at 12:41:28PM -0800, Sean Christopherson wrote: > Apologies for the super slow reply, I put this series on the backburner while I > caught up on other stuff and completely missed your questions. > Never mind :) > On Thu, Jan 19, 2023, Yan Zhao wrote: > > On Thu, Jan 19, 2023 at 10:58:42AM +0800, Zhenyu Wang wrote: > > > Current KVMGT usage is mostly in controlled mode, either user is own host admin, > > > or host admin would pre-configure specific limited number of VMs for KVMGT use. > > > I think printk on error should be fine, we don't need rate limit, and adding > > > extra trace monitor for admin might not be necessary. So I'm towards to keep to > > > use current error message. > > > > > > > Thanks, Sean and Zhenyu. > > So, could I just post the final fix as below? > > No objection here. > > > And, Sean, would you like to include it in this series or should I send it out > > first? > > I'd like to include it in this series as it's necessary (for some definitions of > necessary) to clean up KVM's APIs, and the main benefactor is KVM, i.e. getting > the patch merged sooner than later doesn't really benefit KVMGT itself. > > Thanks much! Then please include it and I can help to test once you sending out next version. Thanks Yan
