[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [ANNOUNCE] Xen 4.15 release update - still in feature freeze
- To: Jan Beulich <jbeulich@xxxxxxxx>
- From: Roger Pau Monné <roger.pau@xxxxxxxxxx>
- Date: Tue, 16 Mar 2021 10:43:23 +0100
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=citrix.com; dmarc=pass action=none header.from=citrix.com; dkim=pass header.d=citrix.com; arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=jY+H3aeiJdIw5LYC3xAbVdwK0B+UdoN9Ybvz3FB+Ugs=; b=m6oXz/IFvG4/+6qrMJxvUwyLnRQRNPhaEU0M6vsbuMs9aDj9rDl4DfFIC3cknm/OtWW0rN17KU82R0Oi9EdI178qBkrWnx9O2tyWbMj3XlOXCfMQoXCfgMga/5lBhifvl3iLGdaKa/a7kjLHNMcVs3DguelvofYto2dUm+p0VGg9vUgw3V00KtSjmm4WrW4wTcNE3DjDG6arXl975FKphcF6OFVi5LrcMlJ0VHXOp/gO7XjxKY/a6sk9fOz2CQxq5fi/ap3EDU1Fuq2uKiKFO0GFnK5ZydgjgXOz64CPu1uZTaw7q2jqmuUZkUUQNQiAvrC1GArMCBChmFgcvW3KAQ==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=FAkT87ypccD2OCHYgJjf/0jzk4xneycbelU19wkKvN1Qob9Q2vq65Opi9w46iq9jc3qCv9T3dH7P3y1zMJUiqAjwwnJUc3YGgtC3mLCRFp6SucgSXh7Z9MA2LiwGwhsTyfPh2pqAfMdNcw2rJecoIyMdgVaGA2Ge2T3PkGQJ5aGPNXjHbFNVZiQoX8m7h7dxQQ/ZQLZr7SHSkcPL8h78RYtIxA0aiudvzjCOIP9r6+tLGF2TtJPrGonsg+TrRDFWMwihauyNn11fVgiYWiD5zcI0Sp/anSOgbMjDBAxDJ74LJ8Wk7P/w5rHveaEUdVP8ABBLo0LtlnoqD05NeSyWCg==
- Authentication-results: esa2.hc3370-68.iphmx.com; dkim=pass (signature verified) header.i=@citrix.onmicrosoft.com
- Cc: Ian Jackson <iwj@xxxxxxxxxxxxxx>, Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, Frédéric Pierret <frederic.pierret@xxxxxxxxxxxx>, Dario Faggioli <dfaggioli@xxxxxxxx>, <committers@xxxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxxx>
- Delivery-date: Tue, 16 Mar 2021 09:43:53 +0000
- Ironport-hdrordr: A9a23:Tcb646pEEETwss8Y+FvWgRAaV5u4KtV00zAX/kB9WHVpW+SivY SHgOkb2RjoiDwYRXEnnpS6NLOdRG7HnKQa3aA4Bp3neAX9omOnIMVZ7YXkyyD9ACGWzIFg/I 9aWexFBNX0ZGIXse/T/BS4H9E8wNOO7aCvgqPkw21wSBxxApsB0y5SIG+gYytLbSNBAoc0E4 fZy8pcvjy7eWkWaMPTPAh5Y8HoodrXmJX6JSMXHhJP0nj1sRqEyp7fVyKZ0BAXTi9Vzd4ZkF TtvgTl6syYwpSG4zDG0Wu71eUzpPLAzZ95CNWImowpLFzX+3qVTaBAf5HHgzwvuuGo7z8R4a nxijMtJd565X+UXkzdm2qU5yDa3Dwj62DvxDaj6BOJy6GJJ0NZerh8rLlUfRfD500rsMsU6t Mx40uju4dKFhSFpSzh5rHzJmBXv3Cpqnkvm/N7tQ0nbaIibtZq3Osi1XIQOpIBECXm0ZsgAe ljAerNjcwmD2+yXjT3uHJiz8erWWl2NhCaQlIassjQ6DROmmtlpnFoiPA3rzMlztYQWpNE7+ PLPuBBk6xPdNYfaeZYCP0aScW6J2TRSXv3QS2vCGWiMJtCF2PGqpbx7rlwzvqtYoY0wJw7n4 mEeE9EtEYpEnieSfGm7dluyFTgUW+9VTPixoV1/J5ioIDxQ7LtLGmqVE0uqc29uP8Sa/erGs qbCdZzObvOPGHuEYFG00nVQJ9JM0QTV8UTp5IVQFSLjsXXKpD7l+DSffrJTYCdUwoMayfaOD 8uTTLzLMJP4gSAQXnjmiXcXHvrZwje8PtLYe3n1tlW7LJIGpxHswATh1j8zNqMMyd+vqs/e1 Y7BLvml6i8tFSn5Gqg1RQsBjNtSmJupJnwWXJDogEHd2nud6wYhtmZcWdOmFyKOwF4VMGTNA JEvVx49eaWIvWrtG4fIuPiFljfo2oYpXqMQZtZsLaE/93ZdpQxCYtjfrdwGwXNHxlcgh1rt2 9HVQ8BSibkZ3DToJTgqKZRKPDUdtF6jgvuC9VTs2jjuUKVotxqemEWRAe0UcmcgR8nQh1dgl EZyd5ZvJOw3RKUbUcviuUxN1NBLECaGqhPAgi+aIJIobzzYw1rQWCWhTuVtgErdgPRhjYvr1 2kCRfRVeDAA1JbtHwd6Krs/V9uXki2fk57aBlBwMZAPFWDnkw2/f6AZ6K13WfUV0ALxfsFNi rZJREIJBl1+tyx3BmJuTqLGHk83K8yNujFALlLScCU5lqdbKmz0Y0WFf5d+5hocO30uugQSO SFZku7Kij7B+5B4X3iml8VfA1P7F8qnvPj1Ee7sCyW3HsjDeHTJ1ojbbcBON2Y53XlQfHN8J gRt6NAgcKAdkHKLviBwuXrShQGDDX5i2u/VfspppBZprhajso6I7DrFR/zkEha1xA/JvrunE wQQK5H8KnMU7UfCvA6SmZ8xB4Vj9yBI0sgjxzuDsI/dV8riWXHP9nh2cu+lZMfRmmArhD3I1 +R7ml0+OrERTKK0dcheugNCFUTTEg383J5+uyeM6XWFQWxbulGuH63KGW0frMYaK+LH9wr31 tHyuDNu++cbCzj3g/M+RN9P6JV6m6iBfqIPzjkI58Az/WKfXKWgqWr58avjDD4DRuDAn5o+r FtRAg3dcRMij4rkYst9DO9I5aH+34Yrw==
- Ironport-sdr: oVJ0cUotRVM93uwQGmpXp3zPVcNc8jcCIaTZ/hEV/xBNLeGwmpZg0vgICNGm9ExVmnKTN9jnhS rly6Dl9PgmMNyXopECexYdVSi1cttvqV16/b8DG0xMOlHfI/0TSYTwM0Ugg+avBYOtAP7mNFsG B2q2IH+K3kEBo3PpKfU0jkIVTQPq7BOV3goptWGImzsWhxpDc22Z+4nKcVnNyASkrwCcpc6nCS sPg2rndGH+JN1QwrB6tZDGy3WLmYflLzIKtJj+8xoYumf+kVV5hW7sGQHIEDzRFXh4d7tdbcY/ Pxw=
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
On Mon, Mar 15, 2021 at 02:46:07PM +0100, Jan Beulich wrote:
> On 15.03.2021 13:18, Ian Jackson wrote:
> > ISSUES BELIEVED NEWLY RESOLVED
> > ==============================
> >
> > Fallout from MSR handling behavioral change.
> >
> > I think there are now no outstanding patches to fix/change MSR
> > behaviour and there is no longer any blocker here ?
>
> In addition to what Andrew has said, while not a blocker in that
> sense I think the excessive verbosity of the logging is also an
> issue.
I think you meant the logging done for each MSR that's not explicitly
handled?
While I agree it might be too verbose, I don't see how we can change
that right now. We could introduce a command line parameter to select
whether to print those messages or not, but I think that's too
specific for a command line option.
We should look into some kind of logging improvements that allow
selecting which messages to print on a per-domain basis IMO.
In any case, those messages will only show up in debug builds, so it's
mostly annoying to developers but transparent to consumers of the
production build.
Thanks, Roger.
|
