Date: Fri, 23 May 2014 23:22:17 +0200 From: Willem Jan Withagen <wjw@digiware.nl> To: Anish <akgupt3@gmail.com>, Andriy Gapon <avg@freebsd.org> Cc: Neel Natu <neel@freebsd.org>, FreeBSD virtualization <freebsd-virtualization@freebsd.org> Subject: Re: bhyve: svm (amd-v) update Message-ID: <537FBC09.9020403@digiware.nl> In-Reply-To: <CALnRwMRpwc=DHib%2BeooftCkSP_K6XtVuR11AceDYju=mMBE2%2Bw@mail.gmail.com> References: <53748481.8010108@FreeBSD.org> <CALnRwMRpwc=DHib%2BeooftCkSP_K6XtVuR11AceDYju=mMBE2%2Bw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 15-5-2014 17:56, Anish wrote: > Hi Andriy, > Thanks for your interest in SVM port of bhyve. I do have patch to sync it > to http://svnweb.freebsd.org/base?view=revision&revision=263780(3/26). If > patches looks good to you, we can submit it. I have been testing it on > Phenom box which lacks some of newer SVM features. Hi, With this patchset I see inb(0x40) calls coming thru to the bhyve VM, where I would expect them to stay down in the VMM dev-driver and emulate the vatpit for that VM. default_inout: port 64, in, bytes 1 default_inout: port 64, in, bytes 1 default_inout: port 67, out, bytes 1 Any particular reason that the IO for that register is not intercepted and ends up in userspace? Any suggestions what to watch for? Not really strong in debuging kernel modules. Thanx, --WjW
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?537FBC09.9020403>